From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: David Sterba <dave@jikos.cz>
Cc: linux-btrfs@vger.kernel.org, chris.mason@oracle.com
Subject: Re: [PATCH] Btrfs: fix missing mutex_unlock in btrfs_del_dir_entries_in_log()
Date: Mon, 25 Apr 2011 08:23:40 +0900 [thread overview]
Message-ID: <4DB4B0FC.7080201@jp.fujitsu.com> (raw)
In-Reply-To: <20110422124556.GV31675@twin.jikos.cz>
(2011/04/22 21:45), David Sterba wrote:
> Hi,
>
> On Fri, Apr 22, 2011 at 06:05:40PM +0900, Tsutomu Itoh wrote:
>> It is necessary to unlock mutex_lock before it return an error when
>> btrfs_alloc_path() fails.
>
> good catch! however I suggest to move the mutex_lock after the
> allocation and check, it'll be semantically equivalent to your change,
> but a bit readable. quick grep for btrfs_alloc_path usage showed that
> it's quite common to do path allocation/check before any real work is
> started.
Even if mutex_lock() move to after btrfs_alloc_path(),
we should call btrfs_end_log_tarns().
So I chose 'goto out_unlock'.
Thanks,
Tsutomu
>
>
> david
>
>> diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
>> index c50271a..f997ec0 100644
>> --- a/fs/btrfs/tree-log.c
>> +++ b/fs/btrfs/tree-log.c
>> @@ -2209,8 +2209,10 @@ int btrfs_del_dir_entries_in_log(struct btrfs_trans_handle *trans,
>>
>> log = root->log_root;
>> path = btrfs_alloc_path();
>> - if (!path)
>> - return -ENOMEM;
>> + if (!path) {
>> + err = -ENOMEM;
>> + goto out_unlock;
>> + }
>
> mutex_lock(...);
>>
>> di = btrfs_lookup_dir_item(trans, log, path, dir->i_ino,
>> name, name_len, -1);
>> @@ -2271,6 +2273,7 @@ int btrfs_del_dir_entries_in_log(struct btrfs_trans_handle *trans,
>> }
>> fail:
>> btrfs_free_path(path);
>> +out_unlock:
>> mutex_unlock(&BTRFS_I(dir)->log_mutex);
>> if (ret == -ENOSPC) {
>> root->fs_info->last_trans_log_full_commit = trans->transid;
>
>
prev parent reply other threads:[~2011-04-24 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 9:05 [PATCH] Btrfs: fix missing mutex_unlock in btrfs_del_dir_entries_in_log() Tsutomu Itoh
2011-04-22 12:45 ` David Sterba
2011-04-24 23:23 ` Tsutomu Itoh [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=4DB4B0FC.7080201@jp.fujitsu.com \
--to=t-itoh@jp.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
/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).