linux-kernel - Re: [PATCH for 2.6.22] [1/10] i386: bug in i386 MTRR initialization

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:	Wed, 20 Jun 2007 14:16:26 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andi Kleen <ak@...e.de>
cc:	righiandr@...rs.sourceforge.net, linux-kernel@...r.kernel.org,
	patches@...-64.org
Subject: Re: [PATCH for 2.6.22] [1/10] i386: bug in i386 MTRR
 initialization

On Wed, 20 Jun 2007, Andi Kleen wrote:
> 
> From: Andrea Righi <righiandr@...rs.sourceforge.net>
>
> BUG: at include/linux/slub_def.h:77 kmalloc_index()

This was never a bug, and should have been named a warning. It's also gone 
in the current source-tree, since we instead of warning now just return 
ZERO_SIZE_PTR, and if somebody then dereferences that zero-sized 
allocation, then that is the *real* bug.

So I'm sure the patch description is misleading, but I'm not sure whether 
the patch itself is wrong per se. But I'm dropping it for now.

		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/