From: Arne Jansen <sensille@gmx.net>
To: chris.mason@oracle.com, linux-btrfs@vger.kernel.org, dave@jikos.cz
Subject: Re: [PATCH v4 3/6] btrfs: add scrub code and prototypes
Date: Thu, 24 Mar 2011 11:25:29 +0100 [thread overview]
Message-ID: <4D8B1C19.7060105@gmx.net> (raw)
In-Reply-To: <20110323171833.GG17108@twin.jikos.cz>
On 23.03.2011 18:18, David Sterba wrote:
> Hi,
>
> I'm reviewing the atomic counters and the wait/wake infrastructure,
> just found two missed mutex_unlock()s in btrfs_scrub_dev() in error
> paths.
>
> On Fri, Mar 18, 2011 at 04:55:06PM +0100, Arne Jansen wrote:
>> This is the main scrub code.
>> + mutex_lock(&fs_info->scrub_lock);
>> + if (dev->scrub_device) {
>> + mutex_unlock(&fs_info->scrub_lock);
> mutex_unlock(&root->fs_info->fs_devices->device_list_mutex);
>
>> + scrub_workers_put(root);
>> + return -EINPROGRESS;
>> + }
>> + sdev = scrub_setup_dev(dev);
>> + if (IS_ERR(sdev)) {
>> + mutex_unlock(&fs_info->scrub_lock);
> mutex_unlock(&root->fs_info->fs_devices->device_list_mutex);
>
>> + scrub_workers_put(root);
>> + return PTR_ERR(sdev);
>> + }
Thanks, I'll add you as Reported-by if that's ok.
-Arne
next prev parent reply other threads:[~2011-03-24 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 15:55 [PATCH v4 0/6] btrfs: scrub Arne Jansen
2011-03-18 15:55 ` [PATCH v4 1/6] btrfs: add parameter to btrfs_lookup_csum_range Arne Jansen
2011-03-18 15:55 ` [PATCH v4 2/6] btrfs: make struct map_lookup public Arne Jansen
2011-03-18 15:55 ` [PATCH v4 3/6] btrfs: add scrub code and prototypes Arne Jansen
2011-03-23 17:18 ` David Sterba
2011-03-24 10:25 ` Arne Jansen [this message]
2011-03-24 14:30 ` David Sterba
2011-03-18 15:55 ` [PATCH v4 4/6] btrfs: sync scrub with commit & device removal Arne Jansen
2011-03-23 17:28 ` David Sterba
2011-03-24 12:58 ` Arne Jansen
2011-03-24 13:48 ` Arne Jansen
2011-03-18 15:55 ` [PATCH v4 5/6] btrfs: add state information for scrub Arne Jansen
2011-03-18 15:55 ` [PATCH v4 6/6] btrfs: new ioctls " Arne Jansen
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=4D8B1C19.7060105@gmx.net \
--to=sensille@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.