linux-kernel - Re: [PATCH 21/41] CacheFiles: Permit the page lock state to be monitored [ver #48]

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: <200904061831.03753.nickpiggin@yahoo.com.au>
Date:	Mon, 6 Apr 2009 18:31:03 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	David Howells <dhowells@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, nfsv4@...ux-nfs.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 21/41] CacheFiles: Permit the page lock state to be monitored [ver #48]

On Sunday 05 April 2009 08:13:33 David Howells wrote:
> Nick Piggin <nickpiggin@...oo.com.au> wrote:
> 
> > On Saturday 04 April 2009 17:09:31 Nick Piggin wrote:
> > > On Saturday 04 April 2009 02:56:24 David Howells wrote:
> > > > Add a function to install a monitor on the page lock waitqueue for a
> > > > particular page, thus allowing the page being unlocked to be detected.
> > > > 
> > > > This is used by CacheFiles to detect read completion on a page in the
> > > > backing filesystem so that it can then copy the data to the waiting
> > > > netfs page.
> > > 
> > > This is the only thing I'm still worried about in core code. The extra
> > > page flag (which is probably unusable for any other fs, due to its
> > > semantics) is an issue, but Andrew seemed like he was willing to spend
> > > *2* page flags on this, so I'm sure he's happy with 1.
> > 
> > Well that is to say it is not a such a bad concept to have...
> 
> What is not such a bad concept to have?  Having an extra page flag?

Notification call when a page read is completed.


> > actually we already have exactly this concept which is what should be used.
> > Ie. the filesystem's io completion handler.
> 
> Which filesystem's I/O completion handler?

Whichever one that you require such information from.
--
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/