linux-kernel - Re: [RFC] Track mlock()ed 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: <20070126031300.59f75b06.akpm@osdl.org>
Date:	Fri, 26 Jan 2007 03:13:00 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Christoph Lameter <clameter@....com>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Track mlock()ed pages

On Thu, 25 Jan 2007 22:36:17 -0800 (PST)
Christoph Lameter <clameter@....com> wrote:

> On Fri, 26 Jan 2007, Nick Piggin wrote:
> 
> > Christoph Lameter wrote:
> > > Add NR_MLOCK
> > > 
> > > Track mlocked pages via a ZVC

Why?

> > I think it is not quite right. You are tracking the number of ptes
> > that point to mlocked pages, which can be >= the actual number of pages.
> 
> Mlocked pages are not inherited. I would expect sharing to be very rare.
>  
> > Also, page_add_anon_rmap still needs to be balanced with page_remove_rmap.
> 
> Hmmm.... 
>  
> > I can't think of an easy way to do this without per-page state. ie.
> > another page flag.
> 
> Thats what I am trying to avoid.

You could perhaps go for a walk across all the other vmas which presently
map this page.  If any of them have VM_LOCKED, don't increment the counter.
Similar on removal: only decrement the counter when the final mlocked VMA
is dropping the pte.

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