linux-kernel - Re: sched: Disallow sched_attr::sched

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, 3 Jun 2014 09:16:09 -0400
From:	Dave Jones <davej@...hat.com>
To:	Richard Weinberger <richard@....at>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michael Kerrisk-manpages <mtk.manpages@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: sched: Disallow sched_attr::sched_policy < 0

On Tue, Jun 03, 2014 at 10:47:18AM +0200, Richard Weinberger wrote:
 > Am 03.06.2014 10:32, schrieb Peter Zijlstra:
 > > On Tue, Jun 03, 2014 at 10:15:44AM +0200, Richard Weinberger wrote:
 > >>> Once upon a time GCC also did warns like that, but my compiler is silent
 > >>> :-(
 > 
 > -Wtype-limits is what you're looking for.
 > 
 > /me currently builds some kernel configs to find out how much noise it triggers...
 
Probably quite a bit I'd bet. There's a load of similar bugs in
coverity's db. Some of them look benign, and are probably there just in
case someone ever changes the type of a var, but it's non-obvious
sometimes if the values a function receives can ever actually be < 0

	Dave

--
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/