From: Arne Jansen <sensille@gmx.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 3/6] btrfs: add scrub code and prototypes
Date: Thu, 17 Mar 2011 20:02:21 +0100 [thread overview]
Message-ID: <4D825ABD.7090108@gmx.net> (raw)
In-Reply-To: <4D814381.9070105@gmx.net>
On 17.03.2011 00:10, Arne Jansen wrote:
> On 16.03.2011 23:07, Andi Kleen wrote:
>> Arne Jansen<sensille@gmx.net> writes:
>>> + */
>>> + mutex_lock(&fs_info->scrub_lock);
>>> + atomic_inc(&fs_info->scrubs_running);
>>> + mutex_unlock(&fs_info->scrub_lock);
>> It seems odd to protect an atomic_inc with a mutex.
>> Is that done for some side effect? Otherwise you either
>> don't need atomic or don't need the lock.
>>
> The reason it is atomic is because it is checked inside a wait_event,
> where I can't hold a lock. The mutex is there to protect the check
> in btrfs_scrub_pause and btrfs_scrub_cancel. But, now that I think
> of it, there is still a race condition left. I'll rethink the locking
> there
> and see if I can eliminate some of the mutex_locks.
On third look I can't find the race condition I thought was there...
Just removing the locks around most inc/dec looks ok.
Thanks,
Arne
next prev parent reply other threads:[~2011-03-17 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 14:50 [PATCH v3 0/6] btrfs: scrub Arne Jansen
2011-03-12 14:50 ` [PATCH v3 1/6] btrfs: add parameter to btrfs_lookup_csum_range Arne Jansen
2011-03-12 14:50 ` [PATCH v3 2/6] btrfs: make struct map_lookup public Arne Jansen
2011-03-12 14:50 ` [PATCH v3 3/6] btrfs: add scrub code and prototypes Arne Jansen
2011-03-13 23:50 ` Ilya Dryomov
2011-03-14 9:57 ` Arne Jansen
2011-03-16 14:35 ` Ilya Dryomov
2011-03-16 14:54 ` Ilya Dryomov
2011-03-16 22:07 ` Andi Kleen
2011-03-16 23:10 ` Arne Jansen
2011-03-17 19:02 ` Arne Jansen [this message]
2011-03-12 14:50 ` [PATCH v3 4/6] btrfs: sync scrub with commit & device removal Arne Jansen
2011-03-12 14:50 ` [PATCH v3 5/6] btrfs: add state information for scrub Arne Jansen
2011-03-12 14:50 ` [PATCH v3 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=4D825ABD.7090108@gmx.net \
--to=sensille@gmx.net \
--cc=andi@firstfloor.org \
--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).