linux-kernel - Re: [PATCH] Make

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, 20 May 2008 08:12:41 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
cc:	Dave Jones <davej@...hat.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Matthew Wilcox <matthew@....cx>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Make

On Tue, 20 May 2008, Alexey Dobriyan wrote:
> 
> Why list_head corruptions are special?

It's not that list corruptions are special, but:
 - *any* corruption is very interesting, and the earlier we find it the 
   better
 - we have a lot of lists in the kernel, so testing pointers is actually 
   likely to find stuff.
 - and lists are something we can *test* for corruption

That third one is important. Most random pointers we can't sanely test 
because they don't have trivial and important patterns.

The second one is relevant too: some of the pointers that we *could* test 
(struct task has a pointer to the thread struct and back, and we could 
test that) are just not common enough to be worth testing. And other 
concepts don't have any nice centralized routines for adding the test.

So no, lists aren't "special" in any inherent way, they are just special 
in these kinds of "incidentally, a lot of random data structure corruption 
has traditionally shown up in lists, because there are so many of them".

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