From: David Howells <dhowells@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>,
David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: page_mkwrite caller is racy?
Date: Thu, 01 Feb 2007 11:44:59 +0000 [thread overview]
Message-ID: <5129.1170330299@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701291521540.24726@blonde.wat.veritas.com>
Hugh Dickins <hugh@veritas.com> wrote:
> > Must it be able to sleep?
>
> Not as David was using it
It absolutely *must* be able to sleep. It has to wait for FS-Cache to finish
writing the page to the cache before letting the PTE be made writable.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>,
David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: page_mkwrite caller is racy?
Date: Thu, 01 Feb 2007 11:44:59 +0000 [thread overview]
Message-ID: <5129.1170330299@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701291521540.24726@blonde.wat.veritas.com>
Hugh Dickins <hugh@veritas.com> wrote:
> > Must it be able to sleep?
>
> Not as David was using it
It absolutely *must* be able to sleep. It has to wait for FS-Cache to finish
writing the page to the cache before letting the PTE be made writable.
David
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-01 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 10:20 page_mkwrite caller is racy? Nick Piggin
2007-01-29 10:20 ` Nick Piggin
2007-01-29 16:08 ` Hugh Dickins
2007-01-29 16:08 ` Hugh Dickins
2007-01-29 20:41 ` Anton Altaparmakov
2007-01-29 20:41 ` Anton Altaparmakov
2007-01-30 1:14 ` Nick Piggin
2007-01-30 1:14 ` Nick Piggin
2007-01-30 1:51 ` Mark Fasheh
2007-01-30 1:51 ` Mark Fasheh
2007-01-30 14:58 ` Anton Altaparmakov
2007-01-30 14:58 ` Anton Altaparmakov
2007-01-31 1:18 ` Nick Piggin
2007-01-31 1:18 ` Nick Piggin
2007-02-01 11:44 ` David Howells [this message]
2007-02-01 11:44 ` David Howells
2007-01-29 20:00 ` Mark Fasheh
2007-01-29 20:00 ` Mark Fasheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5129.1170330299@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.