From: Hillf Danton <hdanton@sina.com>
To: NeilBrown <neilb@suse.de>
Cc: Dave Chinner <david@fromorbit.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/9] Block: switch bd_prepare_to_claim to use ___wait_var_event()
Date: Tue, 20 Aug 2024 19:40:16 +0800 [thread overview]
Message-ID: <20240820114016.873-1-hdanton@sina.com> (raw)
In-Reply-To: <20240819053605.11706-6-neilb@suse.de>
On Mon, 19 Aug 2024 15:20:39 +1000 NeilBrown <neilb@suse.de>
>
> @@ -535,33 +535,23 @@ int bd_prepare_to_claim(struct block_device *bdev, void *holder,
> const struct blk_holder_ops *hops)
> {
> struct block_device *whole = bdev_whole(bdev);
> + int err = 0;
>
> if (WARN_ON_ONCE(!holder))
> return -EINVAL;
> -retry:
> - mutex_lock(&bdev_lock);
> - /* if someone else claimed, fail */
> - if (!bd_may_claim(bdev, holder, hops)) {
> - mutex_unlock(&bdev_lock);
> - return -EBUSY;
> - }
> -
> - /* if claiming is already in progress, wait for it to finish */
> - if (whole->bd_claiming) {
> - wait_queue_head_t *wq = bit_waitqueue(&whole->bd_claiming, 0);
> - DEFINE_WAIT(wait);
>
> - prepare_to_wait(wq, &wait, TASK_UNINTERRUPTIBLE);
> - mutex_unlock(&bdev_lock);
> - schedule();
> - finish_wait(wq, &wait);
> - goto retry;
> - }
> + mutex_lock(&bdev_lock);
> + ___wait_var_event(&whole->bd_claiming,
> + (err = bd_may_claim(bdev, holder, hops)) != 0 || !whole->bd_claiming,
> + TASK_UNINTERRUPTIBLE, 0, 0,
> + mutex_unlock(&bdev_lock); schedule(); mutex_lock(&bdev_lock));
>
At the first glance you add the coding pattern not recommended for the block
directory. Second, you abuse ___wait_var_event() simply because it is available.
> - /* yay, all mine */
> - whole->bd_claiming = holder;
> + /* if someone else claimed, fail */
> + if (!err)
> + /* yay, all mine */
> + whole->bd_claiming = holder;
> mutex_unlock(&bdev_lock);
> - return 0;
> + return err;
> }
> EXPORT_SYMBOL_GPL(bd_prepare_to_claim); /* only for the loop driver */
>
> @@ -571,7 +561,8 @@ static void bd_clear_claiming(struct block_device *whole, void *holder)
> /* tell others that we're done */
> BUG_ON(whole->bd_claiming != holder);
> whole->bd_claiming = NULL;
> - wake_up_bit(&whole->bd_claiming, 0);
> + smp_mb();
> + wake_up_var(&whole->bd_claiming);
Third, worse, you have no real idea why mb is needed.
> }
>
> /**
> --
> 2.44.0
next prev parent reply other threads:[~2024-08-20 11:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 5:20 [PATCH 0/9 RFC] Make wake_up_{bit,var} less fragile NeilBrown
2024-08-19 5:20 ` [PATCH 1/9] i915: remove wake_up on I915_RESET_MODESET NeilBrown
2024-08-19 5:20 ` [PATCH 2/9] Introduce atomic_dec_and_wake_up_var() NeilBrown
2024-08-20 5:47 ` kernel test robot
2024-08-21 5:23 ` kernel test robot
2024-08-19 5:20 ` [PATCH 3/9] XFS: use wait_var_event() when waiting of i_pincount NeilBrown
2024-08-19 5:20 ` [PATCH 4/9] Use wait_var_event() instead of I_DIO_WAKEUP NeilBrown
2024-08-20 7:22 ` Christian Brauner
2024-08-20 19:12 ` Christian Brauner
2024-08-19 5:20 ` [PATCH 5/9] Block: switch bd_prepare_to_claim to use ___wait_var_event() NeilBrown
2024-08-20 4:18 ` Dave Chinner
2024-08-20 21:52 ` NeilBrown
2024-08-28 1:22 ` Dave Chinner
2024-08-28 5:20 ` NeilBrown
2024-08-20 11:40 ` Hillf Danton [this message]
2024-08-21 7:10 ` kernel test robot
2024-08-19 5:20 ` [PATCH 6/9] block/pktdvd: switch congestion waiting to ___wait_var_event() NeilBrown
2024-08-19 5:20 ` [PATCH 7/9] Improve and expand wake_up_bit() interface NeilBrown
2024-08-19 5:20 ` [PATCH 8/9] Improve and extend wake_up_var() interface NeilBrown
2024-08-19 5:20 ` [PATCH 9/9] Use clear_and_wake_up_bit() where appropriate NeilBrown
2024-08-19 6:13 ` [PATCH 0/9 RFC] Make wake_up_{bit,var} less fragile Linus Torvalds
2024-08-20 21:47 ` NeilBrown
2024-08-20 21:58 ` Linus Torvalds
2024-08-20 22:15 ` NeilBrown
2024-08-20 22:24 ` Linus Torvalds
2024-08-19 8:16 ` Christian Brauner
2024-08-19 17:45 ` Linus Torvalds
2024-08-19 20:52 ` NeilBrown
2024-08-19 21:12 ` Linus Torvalds
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=20240820114016.873-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=torvalds@linux-foundation.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