public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Tweedie <sct@redhat.com>,
	adilger@clusterfs.com, Theodore Tso <tytso@MIT.EDU>
Subject: Re: [PATCH 4/4] ext4: check ext4_journal_get_write_access() errors
Date: Tue, 19 Feb 2008 00:19:30 -0800	[thread overview]
Message-ID: <1203409170.3612.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20080217061519.GK3390@APFDCB5C>

On Sun, 2008-02-17 at 15:15 +0900, Akinobu Mita wrote:
> Check ext4_journal_get_write_access() errors.
> 
Acked and added to ext4 patch queue

Mingming
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> Cc: Stephen Tweedie <sct@redhat.com>
> Cc: adilger@clusterfs.com
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Mingming Cao <cmm@us.ibm.com>
> Cc: Theodore Tso <tytso@MIT.EDU>
> ---
>  fs/ext4/namei.c |    9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> Index: 2.6-rc/fs/ext4/namei.c
> ===================================================================
> --- 2.6-rc.orig/fs/ext4/namei.c
> +++ 2.6-rc/fs/ext4/namei.c
> @@ -57,10 +57,15 @@ static struct buffer_head *ext4_append(h
> 
>  	*block = inode->i_size >> inode->i_sb->s_blocksize_bits;
> 
> -	if ((bh = ext4_bread(handle, inode, *block, 1, err))) {
> +	bh = ext4_bread(handle, inode, *block, 1, err);
> +	if (bh) {
>  		inode->i_size += inode->i_sb->s_blocksize;
>  		EXT4_I(inode)->i_disksize = inode->i_size;
> -		ext4_journal_get_write_access(handle,bh);
> +		*err = ext4_journal_get_write_access(handle, bh);
> +		if (*err) {
> +			brelse(bh);
> +			bh = NULL;
> +		}
>  	}
>  	return bh;
>  }

      reply	other threads:[~2008-02-19  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  6:15 [PATCH 4/4] ext4: check ext4_journal_get_write_access() errors Akinobu Mita
2008-02-19  8:19 ` Mingming Cao [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=1203409170.3612.33.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sct@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