linux-kernel - Re: [RFD] Freezing of kernel threads

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:	Sun, 13 May 2007 00:14:46 +0200
From:	Pavel Machek <pavel@....cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Gautham R Shenoy <ego@...ibm.com>,
	Oleg Nesterov <oleg@...sign.ru>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFD] Freezing of kernel threads

Hi!

> > If you fail to do that, we'll see freezer failure, quickly, and catch
> > the simple bug.
> 
> "It's a feature to add crap to drivers and subsystems that don't care!"
> 
> That's a novel thing.
> 
> Maybe we could add other features too. Like a "IM_NOT_AN_IDIOT" flag that 
> every driver has to set in it's "struct device", so that the device 
> manager knows that it wasn't written by an idiot.

Well, it was initially SOMEONE_REVIEWIED_THIS flag (and thus pretty
neccessary for initial merge). Now it still serves as
SOMEONE_REVIEWIED_THIS flag, but I guess you could call it
IM_NOT_AN_IDIOT flag, too.

Well, we can go the other way around, but that means more careful
reviewing of incoming code. Yes, we can do it.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/