From: Paul Bolle <pebolle@tiscali.nl>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: block: ioc->refcount accessed twice in put_io_context()?
Date: Sun, 10 Apr 2011 15:41:40 +0200 [thread overview]
Message-ID: <1302442907.5366.15.camel@t41.thuisdomein> (raw)
0) Looking for clues to solve a problem I ran into, I noticed something
odd in block/blk-ioc.c:put_io_context(). It seems it accesses the atomic
variable ioc->refcount twice in a way which suggests things might race.
1) Code is more exact than words, so this (entirely untested) patch to
solve this possible race might describe better what this is all about:
@@ -33,12 +33,16 @@ static void cfq_dtor(struct io_context *ioc)
*/
int put_io_context(struct io_context *ioc)
{
+ int new;
+
if (ioc == NULL)
return 1;
- BUG_ON(atomic_long_read(&ioc->refcount) == 0);
+ new = atomic_long_dec_return(&ioc->refcount);
+
+ BUG_ON(new < 0);
- if (atomic_long_dec_and_test(&ioc->refcount)) {
+ if (new == 0) {
rcu_read_lock();
cfq_dtor(ioc);
rcu_read_unlock();
Paul Bolle
next reply other threads:[~2011-04-10 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 13:41 Paul Bolle [this message]
2011-04-11 1:54 ` Shaohua Li
2011-04-11 7:42 ` Jens Axboe
2011-04-11 8:45 ` Paul Bolle
2011-04-11 8:53 ` Jens Axboe
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=1302442907.5366.15.camel@t41.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=axboe@kernel.dk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®