linux-kernel - Re: [PATCH -mm 14/24] Ramfs and Ram Disk pages are unevictable

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: <20080612135014.026cc2e3@cuia.bos.redhat.com>
Date:	Thu, 12 Jun 2008 13:50:14 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lee Schermerhorn <lee.schermerhorn@...com>,
	Kosaki Motohiro <kosaki.motohiro@...fujitsu.com>,
	linux-mm@...ck.org, Eric Whitney <eric.whitney@...com>
Subject: Re: [PATCH -mm 14/24] Ramfs and Ram Disk pages are unevictable

On Fri, 13 Jun 2008 03:37:56 +1000
Nick Piggin <nickpiggin@...oo.com.au> wrote:

> > > This isn't the case for brd any longer. It doesn't use the buffer
> > > cache as its backing store, so the buffer cache is reclaimable.

> > I know that pages of files that got paged into the page
> > cache from the ramdisk can be evicted (back to the ram
> > disk), but how do the brd pages themselves behave?
> 
> They are not reclaimable. But they have nothing (directly) to do
> with brd's i_mapping address space, nor are they put on any LRU
> lists.

Ahhhh, doh!

I'm mailing Andrew a patch right now that undoes the
brd.c part of patch 14/24. The ramdisk part is correct
and should stay (afaict).

-- 
All Rights Reversed
--
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/