From: Badari Pulavarty <pbadari@gmail.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [ANNOUNCE] new new aops patchset
Date: Wed, 04 Apr 2007 16:05:19 -0700 [thread overview]
Message-ID: <1175727919.5019.14.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <20070404221034.GF21982@ca-server1.us.oracle.com>
On Wed, 2007-04-04 at 15:10 -0700, Mark Fasheh wrote:
...
> +int pagecache_write_begin(struct file *file, struct address_space *mapping,
> + loff_t pos, unsigned len, unsigned flags,
> + struct page **pagep, void **fsdata)
> +{
> + const struct address_space_operations *aops = mapping->a_ops;
> +
> + if (aops->write_begin) {
> + return aops->write_begin(file, mapping, pos, len, flags,
> + pagep, fsdata);
> + } else {
> + int ret;
> + pgoff_t index = pos >> PAGE_CACHE_SHIFT;
> + unsigned offset = pos & (PAGE_CACHE_SIZE - 1);
> + struct inode *inode = mapping->host;
> + struct page *page;
> +again:
> + page = __grab_cache_page(mapping, index);
> + *pagep = page;
> + if (!page)
> + return -ENOMEM;
> +
> + if (flags & AOP_FLAG_UNINTERRUPTIBLE && !PageUptodate(page)) {
> + /*
> + * There is no way to resolve a short write situation
> + * for a !Uptodate page (except by double copying in
> + * the caller done by generic_perform_write_2copy).
> + *
> + * Instead, we have to bring it uptodate here.
> + */
> + ret = aops->readpage(file, page);
> + page_cache_release(page);
> + if (ret) {
> + if (ret == AOP_TRUNCATED_PAGE)
> + goto again;
> + return ret;
> + }
> + goto again;
> + }
> +
> + ret = aops->prepare_write(file, page, offset, offset+len);
> + if (ret) {
> + if (ret != AOP_TRUNCATED_PAGE)
> + unlock_page(page);
> + page_cache_release(page);
> + if (pos + len > inode->i_size)
> + vmtruncate(inode, inode->i_size);
> + if (ret == AOP_TRUNCATED_PAGE)
> + goto again;
> + }
> + return ret;
> + }
Hmm.. Okay, only filesystems that could return AOP_TRUNCATED_PAGE
are ocf2 and gfs2. Now that both of them are switched to have
write_begin()/write_end(), why do we need this code to handle
AOP_TRUNCATED_PAGE (in the else part) ? Can't we just cleanup/nuke
all the AOP_TRUNCATED_PAGE handling ?
Dumb question ?
Thanks,
Badari
next prev parent reply other threads:[~2007-04-04 23:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 12:09 [ANNOUNCE] new new aops patchset Nick Piggin
2007-04-02 20:18 ` Badari Pulavarty
2007-04-03 0:45 ` Nick Piggin
2007-04-02 20:44 ` Badari Pulavarty
2007-04-02 23:58 ` Nick Piggin
2007-04-03 15:59 ` Badari Pulavarty
2007-04-04 2:33 ` Nick Piggin
2007-04-02 21:44 ` Badari Pulavarty
2007-04-02 23:08 ` Badari Pulavarty
2007-04-02 23:14 ` Badari Pulavarty
2007-04-02 23:49 ` Nick Piggin
2007-04-03 15:57 ` Badari Pulavarty
2007-04-04 2:31 ` Nick Piggin
2007-04-02 23:31 ` Badari Pulavarty
2007-04-02 23:35 ` Nick Piggin
2007-04-02 23:56 ` Badari Pulavarty
2007-04-03 0:02 ` Nick Piggin
2007-04-03 0:00 ` Badari Pulavarty
2007-04-03 0:08 ` Nick Piggin
2007-04-03 9:31 ` Nick Piggin
2007-04-03 16:03 ` Badari Pulavarty
2007-04-04 2:37 ` Nick Piggin
2007-04-03 17:35 ` Badari Pulavarty
2007-04-04 3:05 ` Nick Piggin
2007-04-04 22:10 ` Mark Fasheh
2007-04-04 22:39 ` Badari Pulavarty
2007-04-04 22:51 ` Mark Fasheh
2007-04-04 23:02 ` Badari Pulavarty
2007-04-04 23:05 ` Badari Pulavarty [this message]
2007-04-04 23:17 ` Mark Fasheh
2007-04-04 23:32 ` Badari Pulavarty
2007-04-05 2:08 ` Nick Piggin
2007-04-05 15:21 ` Badari Pulavarty
2007-04-06 1:38 ` Nick Piggin
2007-04-05 2:09 ` Nick Piggin
2007-04-05 0:10 ` David Chinner
2007-04-05 2:13 ` Nick Piggin
2007-04-05 7:45 ` Christoph Hellwig
2007-04-05 7:58 ` Nick Piggin
2007-04-05 2:43 ` David Chinner
2007-04-05 3:00 ` Nick Piggin
2007-04-05 6:18 ` David Chinner
2007-04-05 6:40 ` Nick Piggin
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=1175727919.5019.14.camel@dyn9047017100.beaverton.ibm.com \
--to=pbadari@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=npiggin@suse.de \
--cc=swhiteho@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).