From: Jens Axboe <axboe@kernel.dk>
To: wuchi.zero@gmail.com, mwilck@suse.com, andriy.shevchenko@linux.intel.com
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] lib/sbitmap: Fix invalid loop in __sbitmap_queue_get_batch()
Date: Sat, 25 Jun 2022 11:02:07 -0600 [thread overview]
Message-ID: <165617652775.121867.397759941071832869.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220605145835.26916-1-wuchi.zero@gmail.com>
On Sun, 5 Jun 2022 22:58:35 +0800, wuchi wrote:
> 1. Getting next index before continue branch.
> 2. Checking free bits when setting the target bits. Otherwise,
> it may reuse the busying bits.
>
>
Applied, thanks!
[1/1] lib/sbitmap: Fix invalid loop in __sbitmap_queue_get_batch()
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-25 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 14:58 [PATCH] lib/sbitmap: Fix invalid loop in __sbitmap_queue_get_batch() wuchi
2022-06-17 10:08 ` chi wu
2022-06-24 23:47 ` Martin Wilck
2022-06-25 16:59 ` Jens Axboe
2022-06-25 17:02 ` Jens Axboe [this message]
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=165617652775.121867.397759941071832869.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=wuchi.zero@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).