From: Coly Li <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org, email@example.com, Coly Li <firstname.lastname@example.org>, Geliang Tang <email@example.com>, Hannes Reinecke <firstname.lastname@example.org>, Jens Axboe <email@example.com>, NeilBrown <firstname.lastname@example.org>, Richard Fan <email@example.com>, Vishal L Verma <firstname.lastname@example.org> Subject: [PATCH v4 0/6] badblocks improvement for multiple bad block ranges Date: Thu, 2 Dec 2021 20:52:38 +0800 [thread overview] Message-ID: <email@example.com> (raw) Hi Dan, This is the v4 effort to improve badblocks code APIs to handle multiple ranges in bad block table. Comparing to v3 series, the v4 series modification is for code review comments from Geliang Tang, - Declare local variables in reverse Xmas tree order. - Drop orig_start and orig_len from struct badblocks_context. - Fix typos in code comments. - in badblocks_set() avoid one unnecessary loop by setting variable hint by prev (was prev - 1 in v3 series). There is NO in-memory or on-disk format change in the whole series, all existing API and data structures are consistent. This series just only improve the code algorithm to handle more corner cases, the interfaces are same and consistency to all existing callers (md raid and nvdimm drivers). The original motivation of the change is from the requirement from our customer, that current badblocks routines don't handle multiple ranges. For example if the bad block setting range covers multiple ranges from bad block table, only the first two bad block ranges merged and rested ranges are intact. The expected behavior should be all the covered ranges to be handled. All the patches are tested by modified user space code and the code logic works as expected. The modified user space testing code is provided in last patch. The testing code is an example how the improved code is tested. The whole change is divided into 6 patches to make the code review more clear and easier. If people prefer, I'd like to post a single large patch finally after the code review accomplished. Please review the code and response. Thank you all in advance. Coly Li Cc: Dan Williams <firstname.lastname@example.org> Cc: Geliang Tang <email@example.com> Cc: Hannes Reinecke <firstname.lastname@example.org> Cc: Jens Axboe <email@example.com> Cc: NeilBrown <firstname.lastname@example.org> Cc: Richard Fan <email@example.com> Cc: Vishal L Verma <firstname.lastname@example.org> --- Coly Li (6): badblocks: add more helper structure and routines in badblocks.h badblocks: add helper routines for badblock ranges handling badblocks: improvement badblocks_set() for multiple ranges handling badblocks: improve badblocks_clear() for multiple ranges handling badblocks: improve badblocks_check() for multiple ranges handling badblocks: switch to the improved badblock handling code Coly Li (1): test: user space code to test badblocks APIs block/badblocks.c | 1602 ++++++++++++++++++++++++++++++------- include/linux/badblocks.h | 30 + 2 files changed, 1337 insertions(+), 295 deletions(-) -- 2.31.1
next reply other threads:[~2021-12-02 12:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-02 12:52 Coly Li [this message] 2021-12-02 12:52 ` [PATCH v3 1/6] badblocks: add more helper structure and routines in badblocks.h Coly Li 2021-12-02 12:52 ` [PATCH v3 2/6] badblocks: add helper routines for badblock ranges handling Coly Li 2021-12-09 7:22 ` Geliang Tang 2021-12-10 6:57 ` Coly Li 2021-12-02 12:52 ` [PATCH v3 3/6] badblocks: improvement badblocks_set() for multiple " Coly Li 2021-12-09 7:28 ` Geliang Tang 2021-12-09 18:37 ` Wols Lists 2021-12-10 6:55 ` Coly Li 2021-12-02 12:52 ` [PATCH v3 4/6] badblocks: improve badblocks_clear() " Coly Li 2021-12-09 7:35 ` Geliang Tang 2021-12-02 12:52 ` [PATCH v3 5/6] badblocks: improve badblocks_check() " Coly Li 2021-12-02 12:52 ` [PATCH v3 6/6] badblocks: switch to the improved badblock handling code Coly Li 2021-12-02 12:52 ` [PATCH] test: user space code to test badblocks APIs Coly Li
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 0/6] badblocks improvement for multiple bad block ranges' \ /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
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).