linux-toradex.git/kernel/printk.c, branch T30_LinuxImageV2.0Beta2_20130626

printk: do not handle non-sleepable notification in console_cpu_notify

2011-12-01T05:38:36+00:00

- CPU_DYING should not be handled in sleepable context

Signed-off-by: Minho Ban

kernel: printk: Add non exported function for clearing the log ring buffer

2011-12-01T05:38:13+00:00

Signed-off-by: San Mehat

printk: Fix log_buf_copy termination.

2011-12-01T05:38:11+00:00

If idx was non-zero and the log had wrapped, len did not get truncated
to stop at the last byte written to the log.

Revert "printk: remove unused code from kernel/printk.c"

2011-12-01T05:38:11+00:00

This reverts commit acff181d3574244e651913df77332e897b88bff4.

ARM: Make low-level printk work

2011-12-01T05:37:50+00:00

Makes low-level printk work.

Signed-off-by: Tony Lindgren

kernel/printk: do not turn off bootconsole in printk_late_init() if keep_bootcon

2011-08-25T23:25:34+00:00

It seems that 7bf693951a8e ("console: allow to retain boot console via
boot option keep_bootcon") doesn't always achieve what it aims, as when
printk_late_init() runs it unconditionally turns off all boot consoles.
With this patch, I am able to see more messages on the boot console in
KVM guests than I can without, when keep_bootcon is specified.

I think it is appropriate for the relevant -stable trees.  However, it's
more of an annoyance than a serious bug (ideally you don't need to keep
the boot console around as console handover should be working -- I was
encountering a situation where the console handover wasn't working and
not having the boot console available meant I couldn't see why).

Signed-off-by: Nishanth Aravamudan 
Cc: David S. Miller 
Cc: Alan Cox 
Cc: Greg KH 
Acked-by: Fabio M. Di Nitto 
Cc: 		[2.6.39.x, 3.0.x]
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cap_syslog: don't use WARN_ONCE for CAP_SYS_ADMIN deprecation warning

2011-08-10T01:22:22+00:00

syslog-ng versions before 3.3.0beta1 (2011-05-12) assume that
CAP_SYS_ADMIN is sufficient to access syslog, so ever since CAP_SYSLOG
was introduced (2010-11-25) they have triggered a warning.

Commit ee24aebffb75 ("cap_syslog: accept CAP_SYS_ADMIN for now")
improved matters a little by making syslog-ng work again, just keeping
the WARN_ONCE().  But still, this is a warning that writes a stack trace
we don't care about to syslog, sets a taint flag, and alarms sysadmins
when nothing worse has happened than use of an old userspace with a
recent kernel.

Convert the WARN_ONCE to a printk_once to avoid that while continuing to
give userspace developers a hint that this is an unwanted
backward-compatibility feature and won't be around forever.

Reported-by: Ralf Hildebrandt 
Reported-by: Niels 
Reported-by: Paweł Sikora 
Signed-off-by: Jonathan Nieder 
Liked-by: Gergely Nagy 
Acked-by: Serge Hallyn 
Acked-by: James Morris 
Signed-off-by: Linus Torvalds

printk: Fix console_sem vs logbuf_lock unlock race

2011-06-22T09:39:34+00:00

Fix up the fallout from commit 0b5e1c5255 ("printk: Release
console_sem after logbuf_lock").

The reason for unlocking the console_sem under the logbuf_lock
is that a concurrent printk() might fill up the buffer but fail
to acquire the console sem, resulting in a missed write to the
console until a subsequent console_sem acquire/release cycle.

Signed-off-by: Peter Zijlstra 
Cc: efault@gmx.de
Cc: Linus Torvalds 
Cc: Andrew Morton 
Link: http://lkml.kernel.org/r/1308734409.1022.14.camel@twins
Signed-off-by: Ingo Molnar

printk: Release console_sem after logbuf_lock

2011-06-07T10:50:02+00:00

Release console_sem after unlocking the logbuf_lock so that we don't
generate wakeups while holding logbuf_lock. This avoids some lock
inversion troubles once we remove the lockdep_off bits between
logbuf_lock and rq->lock (prints while holding rq->lock vs doing
wakeups while holding logbuf_lock).

There's of course still an actual deadlock where the printk()s under
rq->lock will issue a wakeup from the up() call, but lockdep won't
warn about that since semaphores are not tracked.

Signed-off-by: Peter Zijlstra 
Cc: Linus Torvalds 
Cc: Andrew Morton 
Link: http://lkml.kernel.org/n/tip-j8swthl12u73h4znbvitljzd@git.kernel.org
Signed-off-by: Ingo Molnar

printk: allocate kernel log buffer earlier

2011-05-25T15:39:48+00:00

On larger systems, because of the numerous ACPI, Bootmem and EFI messages,
the static log buffer overflows before the larger one specified by the
log_buf_len param is allocated.  Minimize the overflow by allocating the
new log buffer as soon as possible.

On kernels without memblock, a later call to setup_log_buf from
kernel/init.c is the fallback.

[akpm@linux-foundation.org: coding-style fixes]
[akpm@linux-foundation.org: fix CONFIG_PRINTK=n build]
Signed-off-by: Mike Travis 
Cc: Yinghai Lu 
Cc: "H. Peter Anvin" 
Cc: Jack Steiner 
Cc: Thomas Gleixner 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds