<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pm24.git/kernel/panic.c, branch v2.6.30-rc4</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.kobert.dev/pm24.git/atom?h=v2.6.30-rc4</id>
<link rel='self' href='https://git.kobert.dev/pm24.git/atom?h=v2.6.30-rc4'/>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/'/>
<updated>2009-04-23T07:36:52Z</updated>
<entry>
<title>locking: clarify kernel-taint warning message</title>
<updated>2009-04-23T07:36:52Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2009-04-23T07:36:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=b48ccb095a0c9257241261ec2bd1cbb1bdabc48b'/>
<id>urn:sha1:b48ccb095a0c9257241261ec2bd1cbb1bdabc48b</id>
<content type='text'>
Andi Kleen reported this message triggering on non-lockdep kernels:

   Disabling lockdep due to kernel taint

Clarify the message to say 'lock debugging' - debug_locks_off()
turns off all things lock debugging, not just lockdep.

[ Impact: change kernel warning message text ]

Reported-by: Andi Kleen &lt;andi@firstfloor.org&gt;
Cc: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>lockdep: continue lock debugging despite some taints</title>
<updated>2009-04-12T14:10:52Z</updated>
<author>
<name>Frederic Weisbecker</name>
<email>fweisbec@gmail.com</email>
</author>
<published>2009-04-11T01:17:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=574bbe782057fdf0490dc7dec906a2dc26363e20'/>
<id>urn:sha1:574bbe782057fdf0490dc7dec906a2dc26363e20</id>
<content type='text'>
Impact: broaden lockdep checks

Lockdep is disabled after any kernel taints. This might be convenient
to ignore bad locking issues which sources come from outside the kernel
tree. Nevertheless, it might be a frustrating experience for the
staging developers or those who experience a warning but are focused
on another things that require lockdep.

The v2 of this patch simply don't disable anymore lockdep in case
of TAINT_CRAP and TAINT_WARN events.

Signed-off-by: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;
Cc: LTP &lt;ltp-list@lists.sourceforge.net&gt;
Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;
Cc: Greg KH &lt;gregkh@suse.de&gt;
LKML-Reference: &lt;1239412638-6739-2-git-send-email-fweisbec@gmail.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>lockdep: warn about lockdep disabling after kernel taint</title>
<updated>2009-04-12T14:10:51Z</updated>
<author>
<name>Frederic Weisbecker</name>
<email>fweisbec@gmail.com</email>
</author>
<published>2009-04-11T01:17:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=9eeba6138cefc0435695463ddadb0d95e0a6bcd2'/>
<id>urn:sha1:9eeba6138cefc0435695463ddadb0d95e0a6bcd2</id>
<content type='text'>
Impact: provide useful missing info for developers

Kernel taint can occur in several situations such as warnings,
load of prorietary or staging modules, bad page, etc...

But when such taint happens, a developer might still be working on
the kernel, expecting that lockdep is still enabled. But a taint
disables lockdep without ever warning about it.
Such a kernel behaviour doesn't really help for kernel development.

This patch adds this missing warning.

Since the taint is done most of the time after the main message that
explain the real source issue, it seems safe to warn about it inside
add_taint() so that it appears at last, without hurting the main
information.

v2: Use a generic helper to disable lockdep instead of an
    open coded xchg().

Signed-off-by: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;
Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;
LKML-Reference: &lt;1239412638-6739-1-git-send-email-fweisbec@gmail.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>panic: clean up kernel/panic.c</title>
<updated>2009-03-13T10:25:53Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2009-03-13T10:14:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=c95dbf27e201587b2a6cf63f8501a0313d9b4801'/>
<id>urn:sha1:c95dbf27e201587b2a6cf63f8501a0313d9b4801</id>
<content type='text'>
Impact: cleanup, no code changed

Clean up kernel/panic.c some more and make it more consistent.

LKML-Reference: &lt;49B91A7E.76E4.0078.0@novell.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>panic, smp: provide smp_send_stop() wrapper on UP too</title>
<updated>2009-03-13T10:24:31Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2009-03-13T10:14:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=d1dedb52acd98bd5e13e1ff4c4d045d58bbd16fe'/>
<id>urn:sha1:d1dedb52acd98bd5e13e1ff4c4d045d58bbd16fe</id>
<content type='text'>
Impact: cleanup, no code changed

Remove an ugly #ifdef CONFIG_SMP from panic(), by providing
an smp_send_stop() wrapper on UP too.

LKML-Reference: &lt;49B91A7E.76E4.0078.0@novell.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>panic: decrease oops_in_progress only after having done the panic</title>
<updated>2009-03-13T10:06:47Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2009-03-13T09:54:24Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=ffd71da4e3f323b7673b061e6f7e0d0c12dc2b49'/>
<id>urn:sha1:ffd71da4e3f323b7673b061e6f7e0d0c12dc2b49</id>
<content type='text'>
Impact: eliminate secondary warnings during panic()

We can panic() in a number of difficult, atomic contexts, hence
we use bust_spinlocks(1) in panic() to increase oops_in_progress,
which prevents various debug checks we have in place.

But in practice this protection only covers the first few printk's
done by panic() - it does not cover the later attempt to stop all
other CPUs and kexec(). If a secondary warning triggers in one of
those facilities that can make the panic message scroll off.

So do bust_spinlocks(0) only much later in panic(). (which code
is only reached if panic policy is relaxed that it can return
after a warning message)

Reported-by: Jan Beulich &lt;jbeulich@novell.com&gt;
LKML-Reference: &lt;49B91A7E.76E4.0078.0@novell.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>stackprotector: update make rules</title>
<updated>2009-02-09T23:41:54Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2009-02-09T13:17:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=5d707e9c8ef2a3596ed5c975c6ff05cec890c2b4'/>
<id>urn:sha1:5d707e9c8ef2a3596ed5c975c6ff05cec890c2b4</id>
<content type='text'>
Impact: no default -fno-stack-protector if stackp is enabled, cleanup

Stackprotector make rules had the following problems.

* cc support test and warning are scattered across makefile and
  kernel/panic.c.

* -fno-stack-protector was always added regardless of configuration.

Update such that cc support test and warning are contained in makefile
and -fno-stack-protector is added iff stackp is turned off.  While at
it, prepare for 32bit support.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>Merge branch 'core/percpu' into stackprotector</title>
<updated>2009-01-18T17:37:14Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2009-01-18T17:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=b2b062b8163391c42b3219d466ca1ac9742b9c7b'/>
<id>urn:sha1:b2b062b8163391c42b3219d466ca1ac9742b9c7b</id>
<content type='text'>
Conflicts:
	arch/x86/include/asm/pda.h
	arch/x86/include/asm/system.h

Also, moved include/asm-x86/stackprotector.h to arch/x86/include/asm.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>oops: increment the oops UUID every time we oops</title>
<updated>2009-01-06T23:59:12Z</updated>
<author>
<name>Arjan van de Ven</name>
<email>arjan@linux.intel.com</email>
</author>
<published>2009-01-06T22:40:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=d6624f996ae539344e8d748cce1117ae7af06fbf'/>
<id>urn:sha1:d6624f996ae539344e8d748cce1117ae7af06fbf</id>
<content type='text'>
... because we do want repeated same-oops to be seen by automated
tools like kerneloops.org

Signed-off-by: Arjan van de Ven &lt;arjan@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>Merge branch 'linus' into stackprotector</title>
<updated>2008-12-31T07:31:57Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2008-12-31T07:31:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=a9de18eb761f7c1c860964b2e5addc1a35c7e861'/>
<id>urn:sha1:a9de18eb761f7c1c860964b2e5addc1a35c7e861</id>
<content type='text'>
Conflicts:
	arch/x86/include/asm/pda.h
	kernel/fork.c
</content>
</entry>
</feed>
