From: Keith Busch <kbusch@kernel.org>
To: dayou5941@163.com
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, liyouhong <liyouhong@kylinos.cn>
Subject: Re: [PATCH] nvme-multipath: require exact iopolicy names for module parameter
Date: Tue, 2 Jun 2026 11:17:56 +0100 [thread overview]
Message-ID: <ah6t1JaF21dkx7dp@kbusch-mbp> (raw)
In-Reply-To: <20260529085143.2016914-1-dayou5941@163.com>
On Fri, May 29, 2026 at 04:51:43PM +0800, dayou5941@163.com wrote:
> From: liyouhong <liyouhong@kylinos.cn>
>
> The iopolicy module parameter uses strncmp prefix matching, so values
> like "numax" are accepted as "numa". The per-subsystem sysfs attribute
> already requires an exact match via sysfs_streq(). Parse both through
> a shared helper so invalid values are rejected consistently.
Thanks, applied to nvme-7.2.
prev parent reply other threads:[~2026-06-02 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 8:51 [PATCH] nvme-multipath: require exact iopolicy names for module parameter dayou5941
2026-06-01 14:44 ` Christoph Hellwig
2026-06-01 15:25 ` John Garry
2026-06-02 10:17 ` Keith Busch [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=ah6t1JaF21dkx7dp@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=dayou5941@163.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=liyouhong@kylinos.cn \
--cc=sagi@grimberg.me \
/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