<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/kernel/printk.c, branch v2.6.36</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.36</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.36'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2010-08-10T03:45:06Z</updated>
<entry>
<title>gcc-4.6: printk: use stable variable to dump kmsg buffer</title>
<updated>2010-08-10T03:45:06Z</updated>
<author>
<name>Andi Kleen</name>
<email>andi@firstfloor.org</email>
</author>
<published>2010-08-10T00:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8c4af38e9b2c2a78369c4e2e5706fe539ac64eb2'/>
<id>urn:sha1:8c4af38e9b2c2a78369c4e2e5706fe539ac64eb2</id>
<content type='text'>
kmsg_dump takes care to sample the global variables
inside a spinlock, but then goes on to use the same
variables outside the spinlock region too.

Use the correct variable. This will make the race
window smaller.

Found by gcc 4.6's new warnings.

Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>printk: fix delayed messages from CPU hotplug events</title>
<updated>2010-08-05T12:25:59Z</updated>
<author>
<name>Kevin Cernekee</name>
<email>cernekee@gmail.com</email>
</author>
<published>2010-06-04T05:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=034260d6779087431a8b2f67589c68b919299e5c'/>
<id>urn:sha1:034260d6779087431a8b2f67589c68b919299e5c</id>
<content type='text'>
When a secondary CPU is being brought up, it is not uncommon for
printk() to be invoked when cpu_online(smp_processor_id()) == 0.  The
case that I witnessed personally was on MIPS:

http://lkml.org/lkml/2010/5/30/4

If (can_use_console() == 0), printk() will spool its output to log_buf
and it will be visible in "dmesg", but that output will NOT be echoed to
the console until somebody calls release_console_sem() from a CPU that
is online.  Therefore, the boot time messages from the new CPU can get
stuck in "limbo" for a long time, and might suddenly appear on the
screen when a completely unrelated event (e.g. "eth0: link is down")
occurs.

This patch modifies the console code so that any pending messages are
automatically flushed out to the console whenever a CPU hotplug
operation completes successfully or aborts.

The issue was seen on 2.6.34.

Original patch by Kevin Cernekee with cleanups by akpm and additional fixes
by Santosh Shilimkar.  This patch superseeds
https://patchwork.linux-mips.org/patch/1357/.

Signed-off-by: Kevin Cernekee &lt;cernekee@gmail.com&gt;
To: &lt;mingo@elte.hu&gt;
To: &lt;akpm@linux-foundation.org&gt;
To: &lt;simon.kagstrom@netinsight.net&gt;
To: &lt;David.Woodhouse@intel.com&gt;
To: &lt;lethal@linux-sh.org&gt;
Cc: &lt;linux-kernel@vger.kernel.org&gt;
Cc: &lt;linux-mips@linux-mips.org&gt;
Reviewed-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
Signed-off-by: Kevin Cernekee &lt;cernekee@gmail.com&gt;
Patchwork: https://patchwork.linux-mips.org/patch/1534/
LKML-Reference: &lt;ede63b5a20af951c755736f035d1e787772d7c28@localhost&gt;
LKML-Reference: &lt;EAF47CD23C76F840A9E7FCE10091EFAB02C5DB6D1F@dbde02.ent.ti.com&gt;
Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
</content>
</entry>
<entry>
<title>printk,kdb: capture printk() when in kdb shell</title>
<updated>2010-05-21T02:04:27Z</updated>
<author>
<name>Jason Wessel</name>
<email>jason.wessel@windriver.com</email>
</author>
<published>2010-05-21T02:04:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d37d39ae3b4a8f9a21114921fb344fe7cadb1abd'/>
<id>urn:sha1:d37d39ae3b4a8f9a21114921fb344fe7cadb1abd</id>
<content type='text'>
Certain calls from the kdb shell will call out to printk(), and any of
these calls should get vectored back to the kdb_printf() so that the
kdb pager and processing can be used, as well as to properly channel
I/O to the polled I/O devices.

CC: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
Acked-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>kdb: core for kgdb back end (2 of 2)</title>
<updated>2010-05-21T02:04:21Z</updated>
<author>
<name>Jason Wessel</name>
<email>jason.wessel@windriver.com</email>
</author>
<published>2010-05-21T02:04:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=67fc4e0cb931d6b4ccf21248e4199b154478ecea'/>
<id>urn:sha1:67fc4e0cb931d6b4ccf21248e4199b154478ecea</id>
<content type='text'>
This patch contains the hooks and instrumentation into kernel which
live outside the kernel/debug directory, which the kdb core
will call to run commands like lsmod, dmesg, bt etc...

CC: linux-arch@vger.kernel.org
Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
Signed-off-by: Martin Hicks &lt;mort@sgi.com&gt;
</content>
</entry>
<entry>
<title>printk: avoid warning when CONFIG_PRINTK is disabled</title>
<updated>2010-03-06T19:26:33Z</updated>
<author>
<name>Gustavo F. Padovan</name>
<email>padovan@profusion.mobi</email>
</author>
<published>2010-03-05T21:42:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cea83886dde49fd7524e9f4a246dd5dff4ad236a'/>
<id>urn:sha1:cea83886dde49fd7524e9f4a246dd5dff4ad236a</id>
<content type='text'>
kernel/printk.c:72: warning: `saved_console_loglevel' defined but not used

Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
Cc: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'next' into for-linus</title>
<updated>2010-02-28T22:36:31Z</updated>
<author>
<name>James Morris</name>
<email>jmorris@namei.org</email>
</author>
<published>2010-02-28T22:36:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b4ccebdd37ff70d349321a198f416ba737a5e833'/>
<id>urn:sha1:b4ccebdd37ff70d349321a198f416ba737a5e833</id>
<content type='text'>
</content>
</entry>
<entry>
<title>syslog: use defined constants instead of raw numbers</title>
<updated>2010-02-04T03:20:41Z</updated>
<author>
<name>Kees Cook</name>
<email>kees.cook@canonical.com</email>
</author>
<published>2010-02-03T23:37:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d78ca3cd733d8a2c3dcd88471beb1a15d973eed8'/>
<id>urn:sha1:d78ca3cd733d8a2c3dcd88471beb1a15d973eed8</id>
<content type='text'>
Right now the syslog "type" action are just raw numbers which makes
the source difficult to follow.  This patch replaces the raw numbers
with defined constants for some level of sanity.

Signed-off-by: Kees Cook &lt;kees.cook@canonical.com&gt;
Acked-by: John Johansen &lt;john.johansen@canonical.com&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
<entry>
<title>syslog: distinguish between /proc/kmsg and syscalls</title>
<updated>2010-02-04T03:20:12Z</updated>
<author>
<name>Kees Cook</name>
<email>kees.cook@canonical.com</email>
</author>
<published>2010-02-03T23:36:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=002345925e6c45861f60db6f4fc6236713fd8847'/>
<id>urn:sha1:002345925e6c45861f60db6f4fc6236713fd8847</id>
<content type='text'>
This allows the LSM to distinguish between syslog functions originating
from /proc/kmsg access and direct syscalls.  By default, the commoncaps
will now no longer require CAP_SYS_ADMIN to read an opened /proc/kmsg
file descriptor.  For example the kernel syslog reader can now drop
privileges after opening /proc/kmsg, instead of staying privileged with
CAP_SYS_ADMIN.  MAC systems that implement security_syslog have unchanged
behavior.

Signed-off-by: Kees Cook &lt;kees.cook@canonical.com&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Acked-by: John Johansen &lt;john.johansen@canonical.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
<entry>
<title>Merge git://git.infradead.org/~dwmw2/mtd-2.6.33</title>
<updated>2010-01-24T18:31:34Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2010-01-24T18:31:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b8be634e01b400fa2528848ad0cd6a5580a15bc4'/>
<id>urn:sha1:b8be634e01b400fa2528848ad0cd6a5580a15bc4</id>
<content type='text'>
* git://git.infradead.org/~dwmw2/mtd-2.6.33:
  mtd: tests: fix read, speed and stress tests on NOR flash
  mtd: Really add ARM pismo support
  kmsg_dump: Dump on crash_kexec as well
</content>
</entry>
<entry>
<title>kmsg_dump: Dump on crash_kexec as well</title>
<updated>2009-12-31T19:45:04Z</updated>
<author>
<name>KOSAKI Motohiro</name>
<email>kosaki.motohiro@jp.fujitsu.com</email>
</author>
<published>2009-12-22T03:15:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0f4bd46ec252887f44f1f065b41867cac8f70dfb'/>
<id>urn:sha1:0f4bd46ec252887f44f1f065b41867cac8f70dfb</id>
<content type='text'>
crash_kexec gets called before kmsg_dump(KMSG_DUMP_OOPS) if
panic_on_oops is set, so the kernel log buffer is not stored
for this case.

This patch adds a KMSG_DUMP_KEXEC dump type which gets called
when crash_kexec() is invoked. To avoid getting double dumps,
the old KMSG_DUMP_PANIC is moved below crash_kexec(). The
mtdoops driver is modified to handle KMSG_DUMP_KEXEC in the
same way as a panic.

Signed-off-by: KOSAKI Motohiro &lt;kosaki.motohiro@jp.fujitsu.com&gt;
Acked-by: Simon Kagstrom &lt;simon.kagstrom@netinsight.net&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
</feed>
