linux-kernel - Re: x86 status was Re: -mm merge plans for 2.6.23

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200707111033.20465.jesse.barnes@intel.com>
Date:	Wed, 11 Jul 2007 10:33:19 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: x86 status was Re: -mm merge plans for 2.6.23

> > i386-trim-memory-not-covered-by-wb-mtrrs.patch
>
> Might need more testing?

For the mtrr trim patch at least, I think the coverage we've received 
in -mm is probably sufficient (the failure mode would be fairly 
obvious).  The only thing I'm nervous about is adding AMD support for 
the quirk, since I don't have any way of testing it.  We can easily add 
that later though, if a tester steps forward or we see demand for it 
(should just be an extra conditional in the trim code).

Thanks,
Jesse
-
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/