linux-kernel - Re: [PATCH, take4] FUTEX : new PRIVATE futexes

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]

Message-ID: <46178676.3010704@cosmosbay.com>
Date:	Sat, 07 Apr 2007 13:54:30 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Jakub Jelinek <jakub@...hat.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Jones <davej@...hat.com>,
	Ulrich Drepper <drepper@...il.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
	Ravikiran G Thirumalai <kiran@...lex86.org>,
	"Shai Fultheim (Shai@...lex86.org)" <shai@...lex86.org>,
	pravin b shelar <pravin.shelar@...softinc.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH, take4] FUTEX : new PRIVATE futexes

Jakub Jelinek a écrit :
> On Sat, Apr 07, 2007 at 10:43:39AM +0200, Eric Dumazet wrote:
>> get_futex_key() does a check against sizeof(u32) regardless of futex being 64bits or not.
>> So it is possible a 64bit futex spans two pages of memory...
> 
> That would be a user bug.  32-bit futexes have to be 32-bit aligned, 64-bit
> futexes have to be 64-bit aligned.

I am not sure what you want to say.

User doing sys_futex64(0x......FFC, FUTEX_WAKE_OP, ...) and crashing kernel or 
corrupting data is ok because its a user bug ?

User is allowed to do anything, kernel must check and protect innocents.
-
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/