linux-kernel - Re: linux-next: Tree for December 11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081216222305.GJ14787@elte.hu>
Date:	Tue, 16 Dec 2008 23:23:05 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alexey Zaytsev <alexey.zaytsev@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: linux-next: Tree for December 11


* Alexey Zaytsev <alexey.zaytsev@...il.com> wrote:

> On Wed, Dec 17, 2008 at 00:08, Ingo Molnar <mingo@...e.hu> wrote:
> 
> >>
> >> The warning can also be reproduced in qemu, so it was easy to bisect.
> >>
> >> commit 7317d7b87edb41a9135e30be1ec3f7ef817c53dd
> >> Author: Nick Piggin <nickpiggin@...oo.com.au>
> >> Date:   Tue Sep 30 20:50:27 2008 +1000
> >>
> >>     sched: improve preempt debugging
> >>
> >>     This patch helped me out with a problem I recently had....
> >>
> >>     Basically, when the kernel lock is held, then preempt_count
> >> underflow does not
> >>     get detected until it is released which may be a long time (and arbitrarily,
> >>     eg at different points it may be rescheduled). If the bkl is released at
> >>     schedule, the resulting output is actually fairly cryptic...
> >>
> >>     With any other lock that elevates preempt_count, it is illegal to schedule
> >>     under it (which would get found pretty quickly). bkl allows scheduling with
> >>     preempt_count elevated, which makes underflows hard to debug.
> >>
> >>     Signed-off-by: Ingo Molnar <mingo@...e.hu>
> >>
> >> I understand that not this particular commit is buggy, but at least
> >> I've got someone to add to the CC. ;)
> >>
> >> Also the author's e-mail looks suspicious.
> >
> > Suspicious in what way?
> 
> Does not appear in signed-off-by.

yes, because i applied and tested it through before Nick was comfortable 
with signing off on it.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/