From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, ericvh@gmail.com
Subject: Re: [RESEND][PATCH] 9p: add write-cache support to loose cache mode
Date: Tue, 13 Feb 2007 16:26:25 -0800 [thread overview]
Message-ID: <20070213162625.0797d156.akpm@linux-foundation.org> (raw)
In-Reply-To: <11714109311262-git-send-email-ericvh@gmail.com>
> On Tue, 13 Feb 2007 17:55:31 -0600 Eric Van Hensbergen <ericvh@gmail.com> wrote:
> +static int v9fs_vfs_writepage(struct page *page, struct writeback_control *wbc)
> +{
> + char *buffer = NULL;
> + struct address_space *mapping = page->mapping;
> + int retval = -EIO;
> + loff_t offset = 0;
> + loff_t pageoffset = 0;
> + unsigned long end_index;
Cosmetic detail: pgoff_t here.
> + int count = PAGE_CACHE_SIZE;
> + struct file *filp = v9fs_find_file(page);
> + struct inode *inode = mapping->host;
> +
> + dprintk(DEBUG_VFS, "page: %p\n", page);
> +
> + if ((!inode) || (!filp))
> + goto UnlockPage;
> +
> + end_index = inode->i_size >> PAGE_CACHE_SHIFT;
> +
> + /* complicated case at end of file */
> + if (page->index >= end_index) {
> + /* things got complicated... */
> + count = inode->i_size & (PAGE_CACHE_SIZE - 1);
> + if (page->index >= end_index + 1 || !count)
> + return 0; /* truncated - don't care */
> + }
> +
> + /* get buffer */
> + buffer = kmap(page) + pageoffset;
kmap_atomic() is faster and less deadlocky. But presumably v9fs_write()
prevents that.
> + offset = ((loff_t) page->index << PAGE_CACHE_SHIFT) + pageoffset;
> +
> + page_cache_get(page);
> +
> + retval = v9fs_write(filp, NULL, buffer, count, &offset);
> +
> + if (retval < 0) {
> + dprintk(DEBUG_ERROR, "error: %d\n", retval);
> + ClearPageUptodate(page);
> + goto UnmapPage;
> + }
I think you'll find that the ->writepage() caller handles all this. The
callers also set AS_EIO, which this code forgot.
> + if (retval < count) {
> + dprintk(DEBUG_ERROR, "Short write\n");
> + }
> +
> + if (offset > inode->i_size) {
> + inode->i_size = offset;
> + }
Can this happen??
If so, mark_inode_dirty() seems to be missing.
> + if (PageError(page))
> + ClearPageError(page);
Is this needed?
> + SetPageUptodate(page);
I'd expect that v9fs_writepage() is only ever called against uptodate pages?
> + retval = 0;
> +
> + UnmapPage:
> kunmap(page);
> + UnlockPage:
> unlock_page(page);
> + page_cache_release(page);
> +
> return retval;
> }
next prev parent reply other threads:[~2007-02-14 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 23:55 Eric Van Hensbergen
2007-02-14 0:16 ` Andrew Morton
2007-02-14 2:07 ` Eric Van Hensbergen
2007-02-14 2:11 ` Andrew Morton
2007-02-14 3:05 ` Nick Piggin
2007-02-14 3:10 ` Andrew Morton
2007-02-14 0:26 ` Andrew Morton [this message]
2007-02-14 0:27 ` Andrew Morton
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=20070213162625.0797d156.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®