From: Ira Weiny <ira.weiny@intel.com>
To: <linan666@huaweicloud.com>, <axboe@kernel.dk>,
<geliang.tang@suse.com>, <xni@redhat.com>, <colyli@suse.de>
Cc: <ira.weiny@intel.com>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linan666@huaweicloud.com>,
<yukuai3@huawei.com>, <yi.zhang@huawei.com>, <houtao1@huawei.com>,
<yangerkun@huawei.com>
Subject: Re: [PATCH 0/4] badblocks: bugfix and cleanup of _badblocks_check()
Date: Sat, 23 Dec 2023 09:28:48 -0800 [thread overview]
Message-ID: <658718d0b8b8d_c613d2948f@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20231223063728.3229446-1-linan666@huaweicloud.com>
linan666@ wrote:
> From: Li Nan <linan122@huawei.com>
>
> Li Nan (4):
> badblocks: goto out if find any unacked badblocks in
> _badblocks_check()
> badblocks: optimize _badblocks_check()
> badblocks: fix slab-out-of-bounds in _badblocks_check()
> badblocks: clean up prev_badblocks()
>
> block/badblocks.c | 48 +++++++++++++++++++++++------------------------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
> --
> 2.39.2
>
Thanks for the series! Unfortunately I'm still seeing some failures with
this series.
Coly's test patch[1] fixed all my test failures. Right off the top I'm
not seeing what you missed that he seemed to catch.
Ira
[1] https://lore.kernel.org/all/nhza4xsnbmcmka7463jxgmdvb27pqvbvcuzs7xp4vzpqlo262d@dp7laevqtaka/
prev parent reply other threads:[~2023-12-23 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 6:37 [PATCH 0/4] badblocks: bugfix and cleanup of _badblocks_check() linan666
2023-12-23 6:37 ` [PATCH 1/4] badblocks: goto out if find any unacked badblocks in _badblocks_check() linan666
2023-12-23 6:37 ` [PATCH 2/4] badblocks: optimize _badblocks_check() linan666
2023-12-23 6:37 ` [PATCH 3/4] badblocks: fix slab-out-of-bounds in _badblocks_check() linan666
2023-12-23 6:37 ` [PATCH 4/4] badblocks: clean up prev_badblocks() linan666
2023-12-23 17:28 ` Ira Weiny [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=658718d0b8b8d_c613d2948f@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=geliang.tang@suse.com \
--cc=houtao1@huawei.com \
--cc=linan666@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xni@redhat.com \
--cc=yangerkun@huawei.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 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).