From: Lars Ellenberg <[email protected]>

Recently introduced al_begin_io_nonblock() was returning -EBUSY,
even when it should return -EWOULDBLOCK.

Impact:
A few spurious wake_up() calls in prepare_al_transaction_nonblock().

Signed-off-by: Philipp Reisner <[email protected]>
Signed-off-by: Lars Ellenberg <[email protected]>
---
 drivers/block/drbd/drbd_actlog.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/drbd/drbd_actlog.c b/drivers/block/drbd/drbd_actlog.c
index 6afe173..6608076 100644
--- a/drivers/block/drbd/drbd_actlog.c
+++ b/drivers/block/drbd/drbd_actlog.c
@@ -389,7 +389,7 @@ int drbd_al_begin_io_nonblock(struct drbd_conf *mdev, 
struct drbd_interval *i)
                if (unlikely(tmp != NULL)) {
                        struct bm_extent  *bm_ext = lc_entry(tmp, struct 
bm_extent, lce);
                        if (test_bit(BME_NO_WRITES, &bm_ext->flags)) {
-                               if (!test_and_set_bit(BME_PRIORITY, 
&bm_ext->flags));
+                               if (!test_and_set_bit(BME_PRIORITY, 
&bm_ext->flags))
                                        return -EBUSY;
                                return -EWOULDBLOCK;
                        }
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to