From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
Cc: "ericvh@gmail.com" <ericvh@gmail.com>,
"rminnich@sandia.gov" <rminnich@sandia.gov>,
"lucho@ionkov.net" <lucho@ionkov.net>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"v9fs-developer@lists.sourceforge.net"
<v9fs-developer@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jack@suse.com" <jack@suse.com>
Subject: Re: [PATCH] 9p: set page uptodate when required in write_end()
Date: Wed, 11 Oct 2017 17:46:49 +0100 [thread overview]
Message-ID: <20171011164649.GA21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20171011122741.doojezq3fe4iyg73@sasha-lappy>
On Wed, Oct 11, 2017 at 12:27:43PM +0000, Levin, Alexander (Sasha Levin) wrote:
> >> diff --git a/fs/9p/vfs_addr.c b/fs/9p/vfs_addr.c
> >> index adaf6f6..e1cbdfd 100644
> >> --- a/fs/9p/vfs_addr.c
> >> +++ b/fs/9p/vfs_addr.c
> >> @@ -310,9 +310,13 @@ static int v9fs_write_end(struct file *filp, struct address_space *mapping,
> >>
> >> p9_debug(P9_DEBUG_VFS, "filp %p, mapping %p\n", filp, mapping);
> >>
> >> - if (unlikely(copied < len && !PageUptodate(page))) {
> >> - copied = 0;
> >> - goto out;
> >> + if (!PageUptodate(page)) {
> >> + if (unlikely(copied < len)) {
> >> + copied = 0;
> >> + goto out;
> >> + } else if (len == PAGE_SIZE) {
> >> + SetPageUptodate(page);
> >> + }
Umm... I'm not sure I like it in that form. Look: to get here
we need to successfully pass through ->write_begin(). Which
means that we either have returned with PageUptodate(page) or
had hit len == PAGE_SIZE && !PageUptodate(page). Case of
non-uptodate with len < PAGE_SIZE is handled by forcing readpage
and repeating the entire thing.
So the only way to get !PageUptodate(page) in ->write_end() is
to have had len == PAGE_SIZE. It needs a comment, at the very
least.
prev parent reply other threads:[~2017-10-11 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 18:46 [PATCH] 9p: set page uptodate when required in write_end() alexander.levin
2017-06-02 2:31 ` Levin, Alexander (Sasha Levin)
2017-10-11 12:27 ` Levin, Alexander (Sasha Levin)
2017-10-11 16:30 ` Linus Torvalds
2017-10-11 16:46 ` Al Viro [this message]
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=20171011164649.GA21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alexander.levin@verizon.com \
--cc=ericvh@gmail.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=rminnich@sandia.gov \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox