From: Joe Thornber <ejt@redhat.com>
To: mpatocka@redhat.com
Cc: dm-devel@redhat.com, Joe Thornber <ejt@redhat.com>
Subject: [PATCH 2/4] Fix a race between reading a new block and having it recycled.
Date: Tue, 2 Aug 2011 15:36:46 +0100 [thread overview]
Message-ID: <1312295808-4323-2-git-send-email-ejt@redhat.com> (raw)
In-Reply-To: <1312295808-4323-1-git-send-email-ejt@redhat.com>
---
drivers/md/persistent-data/dm-block-manager.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/md/persistent-data/dm-block-manager.c b/drivers/md/persistent-data/dm-block-manager.c
index c9fb132..b68be88 100644
--- a/drivers/md/persistent-data/dm-block-manager.c
+++ b/drivers/md/persistent-data/dm-block-manager.c
@@ -447,6 +447,7 @@ static int recycle_block(struct dm_block_manager *bm, dm_block_t where,
* Wait for a block to appear on the empty or clean lists.
*/
spin_lock_irqsave(&bm->lock, flags);
+retry:
while (1) {
/*
* Once we can lock and do io concurrently then we should
@@ -486,7 +487,11 @@ static int recycle_block(struct dm_block_manager *bm, dm_block_t where,
spin_lock_irqsave(&bm->lock, flags);
__wait_io(b, &flags);
- /* FIXME: Can b have been recycled between io completion and here? */
+ /*
+ * Has b been recycled whilst we were unlocked?
+ */
+ if (b->where != where)
+ goto retry;
/*
* Did the io succeed?
--
1.7.4.1
next prev parent reply other threads:[~2011-08-02 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 21:00 Review of dm-block-manager.c Mikulas Patocka
2011-08-01 21:17 ` Mike Snitzer
2011-08-02 0:15 ` Mike Snitzer
2011-08-02 0:30 ` Mike Snitzer
2011-08-02 13:07 ` Joe Thornber
2011-08-02 13:29 ` Joe Thornber
2011-08-02 14:36 ` [PATCH 1/4] The return code from the various wait functions is never acted upon. So change to uninterrupible waits and change the return type to void Joe Thornber
2011-08-02 14:36 ` Joe Thornber [this message]
2011-08-03 14:53 ` [PATCH 2/4] Fix a race between reading a new block and having it recycled Mikulas Patocka
2011-08-02 14:36 ` [PATCH 3/4] [block-manager] remove spurious decrement of write_lock_pending in the case of a recycled block Joe Thornber
2011-08-03 14:50 ` Mikulas Patocka
2011-08-04 9:06 ` Joe Thornber
2011-08-02 14:36 ` [PATCH 4/4] Track errored blocks Joe Thornber
2011-08-03 15:00 ` Mikulas Patocka
2011-08-03 14:42 ` [PATCH 1/4] The return code from the various wait functions is never acted upon. So change to uninterrupible waits and change the return type to void Mikulas Patocka
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=1312295808-4323-2-git-send-email-ejt@redhat.com \
--to=ejt@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.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 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.