[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ae62f34f-149c-77df-f864-2db653774715@huaweicloud.com>
Date: Thu, 17 Aug 2023 09:22:35 +0800
From: Li Nan <linan666@...weicloud.com>
To: axboe@...nel.dk, vishal.l.verma@...el.com,
dan.j.williams@...el.com, ashok_raj@...ux.intel.com
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
yukuai3@...wei.com, yi.zhang@...wei.com, houtao1@...wei.com,
yangerkun@...wei.com
Subject: Re: [PATCH v4 0/4] block/badblocks: fix badblocks setting error
在 2023/6/26 16:09, linan666@...weicloud.com 写道:
> From: Li Nan <linan122@...wei.com>
>
> This patch series fixes some simple bugs of setting badblocks and
> optimizing struct badblocks. Coly Li has been trying to refactor badblocks
> in patch series "badblocks improvement for multiple bad block ranges"
> (https://lore.kernel.org/all/20220721121152.4180-1-colyli@suse.de). but the
Coly has sent the lastest version of his patch series.
Now this patch series can be discarded.
> workload is significant. Before that, I will fix some easily triggered
> issues and optimize some code that does not conflict with Coly's changes.
>
> Changes in v4:
> - patch 1, remove the part of reorder fields
> - patch 3/4, improve commit log.
>
> Changes in v3:
> - delete patchs with significant changes.
>
> Li Nan (4):
> block/badblocks: change some members of badblocks to bool
> block/badblocks: only set bb->changed/unacked_exist when badblocks
> changes
> block/badblocks: fix badblocks loss when badblocks combine
> block/badblocks: fix the bug of reverse order
>
> include/linux/badblocks.h | 9 +++++----
> block/badblocks.c | 38 ++++++++++++++++++++++----------------
> 2 files changed, 27 insertions(+), 20 deletions(-)
>
--
Thanks,
Nan
Powered by blists - more mailing lists