From: Yu Kuai <yukuai1@huaweicloud.com>
To: axboe@kernel.dk, asml.silence@gmail.com, osandov@fb.com, jack@suse.cz
Cc: kbusch@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yukuai1@huaweicloud.com, yi.zhang@huawei.com
Subject: [PATCH RFC v3 0/3] bugfix for sbitmap
Date: Sun, 10 Jul 2022 12:21:57 +0800 [thread overview]
Message-ID: <20220710042200.20936-1-yukuai1@huaweicloud.com> (raw)
Changes in v3:
- rename patch 2, and add some comments.
- add patch 3, which fixes a new issue pointed out by Jan Kara.
Changes in v2:
- split to spearate patches for different problem.
- add fix tag
This patchset fixes problems in the wakeup path on concurrent scenarios,
the problems are found during code review, and it's not reporduced in
real test yet in my environment.
Keith reported a possible related io hung problem in nvme:
https://bugzilla.kernel.org/show_bug.cgi?id=215679
Previous versions:
v1: https://lore.kernel.org/all/20220617141125.3024491-1-yukuai3@huawei.com/
v2: https://lore.kernel.org/all/20220619080309.1630027-1-yukuai3@huawei.com/
Yu Kuai (3):
sbitmap: fix that same waitqueue can be woken up continuously
sbitmap: fix invalid wakeup on the wrong waitqueue
sbitmap: fix that 'wait_cnt' can be decreased while waitqueue is empty
lib/sbitmap.c | 70 +++++++++++++++++++++++++++++++--------------------
1 file changed, 43 insertions(+), 27 deletions(-)
--
2.31.1
next reply other threads:[~2022-07-10 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 4:21 Yu Kuai [this message]
2022-07-10 4:21 ` [PATCH RFC v3 1/3] sbitmap: fix that same waitqueue can be woken up continuously Yu Kuai
2022-07-11 14:20 ` Jan Kara
2022-07-12 13:25 ` Yu Kuai
2022-07-10 4:21 ` [PATCH RFC v3 2/3] sbitmap: fix invalid wakeup on the wrong waitqueue Yu Kuai
2022-07-11 14:26 ` Jan Kara
2022-07-12 13:26 ` Yu Kuai
2022-07-10 4:22 ` [PATCH RFC v3 3/3] sbitmap: fix that 'wait_cnt' can be decreased while waitqueue is empty Yu Kuai
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=20220710042200.20936-1-yukuai1@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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.