linux-kernel - Re: Revert needed: udev spewing warnons on common systems in 3.0

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:	Tue, 2 Aug 2011 14:50:19 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Revert needed: udev spewing warnons on common systems in 3.0

On Tue, 2 Aug 2011, Andi Kleen wrote:

> And that's fine because nothing is fundamentally broken here that
> needs urgent fixing (except for that bogus backtrace of course)
> 

Maybe not urgent, but needs to be fixed within the next 12 months because 
all of the users of /proc/pid/oom_adj thus far have been to disable oom 
killing for the thread and that protection isn't guaranteed when the 
tunable is removed.  Doing echo -17 > /proc/pid/oom_adj is a pretty good 
indicator that the process is important.

> The right way is to add a one linker printk_once and then just wait
> for a few years.
> 

This is what I did, except I waited one year instead of a few and now I 
wanted to add a more verbose warning for those that still haven't been 
fixed because we're one year away from the tunable's scheduled removal.  
If you're going to reply with a concern about the stack trace again, 
please see my patch I posted for Linus if the kernel log parsers are 
really that delicate.
--
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/