From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org, colyli@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 0/3] Validation for names during creation
Date: Wed, 21 Dec 2022 12:50:16 +0100 [thread overview]
Message-ID: <20221221115019.26276-1-mariusz.tkaczyk@linux.intel.com> (raw)
Hi Jes, Coly
Mdadm has to weak names policy and it is inconsistency with udev.
From IMSM side it also causes problem with VROC UEFI driver.
There is a small risk of regression because print_escape() is removed.
I think that these cases are incidental and can be fixed by updating
array name. All test passed.
Mariusz Tkaczyk (3):
mdadm: create ident_init()
mdadm: refactor ident->name handling
Limit length and set of characters allowed of devname
Detail.c | 8 ++---
config.c | 81 ++++++++++++++++++++++++++++++++++---------------
lib.c | 80 +++++++++++++++++++++++++++++++++++++++---------
mdadm.8.in | 57 +++++++++++++++++-----------------
mdadm.c | 32 ++++---------------
mdadm.conf.5.in | 4 ---
mdadm.h | 32 +++++++++++++------
super-intel.c | 25 +++++----------
super1.c | 3 +-
util.c | 24 +++++++++++++++
10 files changed, 212 insertions(+), 134 deletions(-)
--
2.26.2
next reply other threads:[~2022-12-21 11:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:50 Mariusz Tkaczyk [this message]
2022-12-21 11:50 ` [PATCH 1/3] mdadm: create ident_init() Mariusz Tkaczyk
2022-12-28 15:05 ` Jes Sorensen
2022-12-21 11:50 ` [PATCH 2/3] mdadm: refactor ident->name handling Mariusz Tkaczyk
2022-12-28 15:07 ` Jes Sorensen
2022-12-29 9:39 ` Mariusz Tkaczyk
2023-01-09 10:51 ` Mariusz Tkaczyk
2023-03-02 14:52 ` Jes Sorensen
2023-03-03 12:04 ` Mariusz Tkaczyk
2023-03-08 19:04 ` Jes Sorensen
2023-03-09 8:02 ` Mariusz Tkaczyk
2023-03-10 14:43 ` Jes Sorensen
2022-12-21 11:50 ` [PATCH 3/3] Limit length and set of characters allowed of devname Mariusz Tkaczyk
2023-03-13 14:22 ` Jes Sorensen
2023-03-14 8:14 ` 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=20221221115019.26276-1-mariusz.tkaczyk@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=colyli@suse.de \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.