linux-kernel - Re: [PATCH] trim memory not covered by WB MTRRs

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:	Thu, 7 Jun 2007 15:25:00 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Jesse Barnes" <jesse.barnes@...el.com>,
	"Justin Piszcz" <jpiszcz@...idpixels.com>,
	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs

On 6/7/07, Andi Kleen <andi@...stfloor.org> wrote:
> On Wed, Jun 06, 2007 at 04:27:46PM -0700, Jesse Barnes wrote:
> > [...]
> > I'm not sure it's appropriate for -rc5 since it mucks around with some
> > early boot ordering, but I'll leave that to Andi, since it does address
> > some real bugs people have been seeing.
>
> I don't think the patch is suitable for merging at this time. Perhaps
> if it survives some time in -mm* / 2.6.23* it could be backported
> in a later 2.6.22 stable release. But right now it definitely
> needs more testing and addressing of my review comments.

BTW an unrelated/happy side-effect of the patch is that it removes
the zero-size-guilty kmalloc()'s from the mtrr code. -mm does have
some fixes that prevent those zero-size allocations, which could
likely be retired if this gets merged in? ...

[ On another unrelated note, could someone tell me who maintains
i386? I've looked around, but surprisingly can't seem to find
anybody listed anywhere. ]

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