From: Theodore Ts'o <tytso@mit.edu>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: 'Dan Carpenter' <dan.carpenter@oracle.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Ashish Sangwan <a.sangwan@samsung.com>
Subject: Re: [PATCH] ext4: fix missing unlock on error in collapse range
Date: Tue, 27 May 2014 12:48:20 -0400 [thread overview]
Message-ID: <20140527164820.GC1158@thunk.org> (raw)
In-Reply-To: <000601cf793f$e5377070$afa65150$@samsung.com>
On Tue, May 27, 2014 at 09:09:15AM +0900, Namjae Jeon wrote:
> Add i_write_mutex unlock on the error handling path in collapse_range().
>
> Cc: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> ---
> fs/ext4/extents.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Thanks for the patch!
This is the increment diff which I'm going to apply instead. It
results in a net decrease of one line of code, instead of a net
increase of two, and it is more consistent in terms of the error
handling style.
Cheers,
- Ted
fs/ext4/extents.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 8ffab40..cb23a34 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -5423,10 +5423,8 @@ int ext4_collapse_range(struct inode *inode, loff_t offset, loff_t len)
/* Call ext4_force_commit to flush all data in case of data=journal. */
if (ext4_should_journal_data(inode)) {
ret = ext4_force_commit(inode->i_sb);
- if (ret) {
- mutex_unlock(&EXT4_I(inode)->i_write_mutex);
- return ret;
- }
+ if (ret)
+ goto out_i_write_mutex;
}
/*
@@ -5439,7 +5437,7 @@ int ext4_collapse_range(struct inode *inode, loff_t offset, loff_t len)
ret = filemap_write_and_wait_range(inode->i_mapping, ioffset,
LLONG_MAX);
if (ret)
- return ret;
+ goto out_i_write_mutex;
/* Take mutex lock */
mutex_lock(&inode->i_mutex);
@@ -5512,6 +5510,7 @@ out_dio:
ext4_inode_resume_unlocked_dio(inode);
out_mutex:
mutex_unlock(&inode->i_mutex);
+out_i_write_mutex:
mutex_unlock(&EXT4_I(inode)->i_write_mutex);
return ret;
}
next prev parent reply other threads:[~2014-05-27 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 0:09 [PATCH] ext4: fix missing unlock on error in collapse range Namjae Jeon
2014-05-27 16:48 ` Theodore Ts'o [this message]
2014-05-28 0:15 ` Namjae Jeon
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=20140527164820.GC1158@thunk.org \
--to=tytso@mit.edu \
--cc=a.sangwan@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=namjae.jeon@samsung.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).