From: Jes Sorensen <jes@trained-monkey.org>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: linux-raid@vger.kernel.org, colyli@suse.de
Subject: Re: [PATCH v2 0/6] mdadm: POSIX portable naming rules
Date: Thu, 26 Oct 2023 17:31:59 -0400 [thread overview]
Message-ID: <ff7cc9e9-532b-5a23-cdb7-e6b4521a2004@trained-monkey.org> (raw)
In-Reply-To: <20230601072750.20796-1-mariusz.tkaczyk@linux.intel.com>
On 6/1/23 03:27, Mariusz Tkaczyk wrote:
> Hi Jes,
> To avoid problem with udev and VROC UEFI driver I developed stronger
> naming policy, basing on POSIX portable names standard. Verification is
> added for names and config entries. In case of an issue, user can update
> name to make it compatible (for IMSM and native).
>
> The changes here may cause /dev/md/ link will be different than before
> mdadm update. To make any of that happen user need to use unusual naming
> convention, like:
> - special, non standard signs like, $,%,&,* or space.
> - '-' used as first sign.
> - locals.
>
> Note: I didn't analyze configurations with "names=1". If name cannot be
> determined mdadm should fallback to default numbered dev creation.
>
> If you are planning release soon then feel free to merge it after the
> release. It is a potential regression point.
>
> It is a new version of [1] but it is strongly rebuild. Here is a list
> of changes:
> 1. negative and positive test scenarios for both create and config
> entries are added.
> 2. Save parsed parameters in dedicated structs. It is a way to control
> what is parsed, assuming that we should use dedicated set_* function.
> 3. Verification for config entries is added.
> 5. Improved error logging for names:
> - during creation, these messages are errors, printed to stderr.
> - for config entries, messages are just a warnings printed to stdout.
> 6. Error messages reworked.
> 7. Updates in manual.
>
> [1] https://lore.kernel.org/linux-raid/20221221115019.26276-1-mariusz.tkaczyk@linux.intel.com/
>
> Mariusz Tkaczyk (6):
> tests: create names_template
> tests: create 00confnames
> mdadm: set ident.devname if applicable
> mdadm: refactor ident->name handling
> mdadm: define ident_set_devname()
> mdadm: Follow POSIX Portable Character Set
Applied!
Thanks,
Jes
next prev parent reply other threads:[~2023-10-26 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 7:27 [PATCH v2 0/6] mdadm: POSIX portable naming rules Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 1/6] tests: create names_template Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 2/6] tests: create 00confnames Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 3/6] mdadm: set ident.devname if applicable Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 4/6] mdadm: refactor ident->name handling Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 5/6] mdadm: define ident_set_devname() Mariusz Tkaczyk
2023-06-01 7:27 ` [PATCH 6/6] mdadm: Follow POSIX Portable Character Set Mariusz Tkaczyk
2024-07-25 13:30 ` Nigel Croxon
2024-07-25 13:34 ` Nigel Croxon
2023-06-01 8:57 ` [PATCH v2 0/6] mdadm: POSIX portable naming rules Paul Menzel
2023-06-01 9:52 ` Mariusz Tkaczyk
2023-10-26 21:31 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-01 12:32 Stefan Fleischmann
2024-01-03 8:53 ` Mariusz Tkaczyk
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=ff7cc9e9-532b-5a23-cdb7-e6b4521a2004@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.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).