linux-kernel - Re: [PATCH] [2/16] POISON: Add page flag for poisoned pages

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: <20090408062441.GF17934@one.firstfloor.org>
Date:	Wed, 8 Apr 2009 08:24:41 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, x86@...nel.org
Subject: Re: [PATCH] [2/16] POISON: Add page flag for poisoned pages

On Tue, Apr 07, 2009 at 10:14:21PM -0700, Andrew Morton wrote:
> On Tue,  7 Apr 2009 17:09:58 +0200 (CEST) Andi Kleen <andi@...stfloor.org> wrote:
> 
> > Poisoned pages need special handling in the VM and shouldn't be touched 
> > again. This requires a new page flag. Define it here.
> 
> I wish this patchset didn't change/abuse the well-understood meaning of
> the word "poison".

Sorry, that's the terminology on the hardware side.

If there's much confusion I could rename it HwPoison or somesuch?

> > The page flags wars seem to be over, so it shouldn't be a problem
> > to get a new one. I hope.
> 
> They are?  How did it all get addressed?

Allowing 64bit to use more and using [V]SPARSEMAP to limit flags
use for zones. I think.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/