From: Jan Kara <jack@suse.cz>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Return error if we fail to allocate block in noalloc_get_block_write
Date: Tue, 7 Jul 2009 19:18:07 +0200 [thread overview]
Message-ID: <20090707171807.GD24457@duck.suse.cz> (raw)
In-Reply-To: <20090701095636.GB20540@skywalker>
On Wed 01-07-09 15:26:36, Aneesh Kumar K.V wrote:
> On Wed, Jul 01, 2009 at 03:16:15PM +0530, Aneesh Kumar K.V wrote:
> > block_write_full_page consider a zero return from get_block as success.
> > noalloc_get_block_write returned zero even if we failed to find a mapping
> > blocks. Returning non zero ensures we fallback to the error handling path
> > of block_write_full_page which would properly redirty the page after
> > the below patch is applied.
> >
> > http://article.gmane.org/gmane.linux.file-systems/33145
> >
> > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> > ---
> >
> > NOTE: I am not sure whether -EGAIN is the right error to be returned error.
> > This patch should enable us to push the pending ext4 patches in the patch
> > queue without depending on the full series from Jan. Will reply to this
> > email with patch ordering.
> >
> > fs/ext4/inode.c | 5 ++++-
> > 1 files changed, 4 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> > index 25638bc..6c814af 100644
> > --- a/fs/ext4/inode.c
> > +++ b/fs/ext4/inode.c
> > @@ -2514,7 +2514,10 @@ static int noalloc_get_block_write(struct inode *inode, sector_t iblock,
> > if (ret > 0) {
> > bh_result->b_size = (ret << inode->i_blkbits);
> > ret = 0;
> > - }
> > + } else if (create && ret == 0)
> > + /* write request on unmapped buffer head. */
> > + ret = -EAGAIN;
> > +
> > return ret;
> > }
> >
>
> The patch ordering I tested this with was
> + stable-boundary
> + stable-boundary-undo.patch
> + jan-kara-dont-clear-dirty-bits-in-block_write_full_page
> + dont-look-at-buffer_heads-outside-i_size
> + fix-mmap-truncate-race-with-subpage-blocksize
> + 01.patch <=============================================== This is the above patch
> + fix-mmap-truncate-race-with-nondelalloc
> + move-__ext4_journaled-writepage-function
> + add-WARN_ON-with-unmapped-dirty-bh-in-writepage
> + vfs-jan-kara-page_mkwrite-infrastructure
> + allocate-blocks-correctly-with-subpage-blocksize
> > jan-kara-unmap-underlying-metadata-of-new-buffers-only-when-mapped
>
> Now with jan-kara-dont-clear-dirty-bits-in-block_write_full_page
> block_write_full_page will redirty the page when get_block fails. That
> would ensure that we don't drop the pages if we find unmapped
> buffer_heads in the writepage callback. The patch
> fix-mmap-truncate-race-with-subpage-blocksize actually pass pages with
> unmapped buffer heads to block_write_full_page.
>
> This also means we can push patches upto
> move-__ext4_journaled-writepage-function to upstream in 2.6.31
>
> I am yet to run the full patch set on ABAT. So the patches had limited
> testing.
Yes, this looks as a good solution to me since Nick had some objections
to later patches in my patchset so they probably won't get merged for
2.6.31...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2009-07-07 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 9:46 [PATCH] ext4: Return error if we fail to allocate block in noalloc_get_block_write Aneesh Kumar K.V
2009-07-01 9:56 ` Aneesh Kumar K.V
2009-07-07 17:18 ` Jan Kara [this message]
2009-07-07 9:20 ` Aneesh Kumar K.V
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=20090707171807.GD24457@duck.suse.cz \
--to=jack@suse.cz \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).