Re: [PATCH 11/22] CacheFiles: Permit the page lock state to be monitored

Trond Myklebust <Trond.Myklebust@netapp.com> wrote:

> > 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.
>
> Won't it in any case want to lock the page too?

No. Why would it? All it wants to do is to read the page (copying it to the netfs's page), assuming it becomes PG_uptodate.

> That would be the only way to ensure that the page is still mapped into the
> address space when you're writing it out...

I don't understand what you're getting at. Write the page out where? We've just read it in from the cache, so why would we be writing it back out?

David
-
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

• This message: [ Message body ]
• Next message: David Howells: "Re: [PATCH 00/22] Introduce credential record"
• Previous message: David Howells: "[PATCH 02/22] CRED: Split the task security data and move part of it into struct cred"
• In reply to: Trond Myklebust: "Re: [PATCH 11/22] CacheFiles: Permit the page lock state to be monitored"
• Next in thread: David Howells: "[PATCH 17/22] AFS: Add TestSetPageError()"

• Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ]