linux-kernel - Re: Linux 2.6.28-rc8

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]

Date:	Fri, 12 Dec 2008 07:57:46 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Frans Pop <elendil@...net.nl>, Eric Anholt <eric@...olt.net>,
	nix.or.die@...glemail.com, linux-kernel@...r.kernel.org,
	rjw@...k.pl, Yinghai Lu <yinghai@...nel.org>
Subject: Re: Linux 2.6.28-rc8

On Fri, 12 Dec 2008 09:24:56 +0100
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Pekka Enberg <penberg@...helsinki.fi> wrote:
> 
> > Hi Ingo,
> > 
> > On Thu, Dec 11, 2008 at 10:36 PM, Ingo Molnar <mingo@...e.hu> wrote:
> > > ok. In this case i'd suggest we should just remove the warning.
> > > People do get scared by needless kernel stack dumps - no matter
> > > whether it's marked informational or not.
> > >
> > > So how about the patch below, queued up in tip/x86/debug? Arjan,
> > > what do you think?
> > 
> > How come we don't put it under CONFIG_X86_DEBUG or something and
> > hide somewhere in the "Kernel debugging" menu?
> 
> okay - how about the following then instead - we still keep the
> warning, but do various things to make it appear less scary.

another thing we could do is try to only warn if you cross bar
boundaries but not if you cross other user-of-the-resource boundaries.
--
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/