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: <1236930985.5188.77.camel@laptop>
Date:	Fri, 13 Mar 2009 08:56:25 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Minchan Kim <minchan.kim@...il.com>
Cc:	Jamie Lokier <jamie@...reable.org>,
	uClinux development list <uclinux-dev@...inux.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Howells <dhowells@...hat.com>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [uClinux-dev] RE: [PATCH] NOMMU: Pages allocated to a ramfs
 inode's pagecache may get wrongly discarded

On Fri, 2009-03-13 at 08:20 +0900, Minchan Kim wrote:

> > > Does the vm pageout logic include or skip these "dirty" pages looking
> > > for candidates to flush to storage?  What about with MMU?
> > 
> > Includes them, regular pageout will try to do the writeout to clean them
> > and then discard them. 
> > 
> > The ramfs stuff is rather icky in that it adds the pages to the aging
> > list, marks them dirty, but does not provide a writeout method. 
> > 
> > This will make the paging code scan over them (continuously) trying to
> > clean them, failing that (lack of writeout method) and putting them back
> > on the list.
> 
> It ins't true any more. 
> UNEVICTABLE_LRU will move ramfs's page from LRU to unevictable list.
> Couldn't we solve this problem if NOMMU can support CONFIG_UNEVICTABLE_LRU ?

That's more of a band-aid than a solution, no? They should never have
been on the list to begin with.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ