From: Mariusz Tkaczyk <mtkaczyk@kernel.org>
To: "Masalkhi, Abd Alrhman" <abd.masalkhi@gatech.edu>
Cc: "blazej.kucman@graidtech.com" <blazej.kucman@graidtech.com>,
"ncroxon@redhat.com" <ncroxon@redhat.com>,
"xni@redhat.com" <xni@redhat.com>,
"song@kernel.org" <song@kernel.org>,
"yukuai@kernel.org" <yukuai@kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] mdadm: Deprecate the obsolete --auto-detect option
Date: Wed, 28 Oct 2026 15:00:47 +0100 [thread overview]
Message-ID: <20261028150047.688d2120@kernel.org> (raw)
In-Reply-To: <m25wym2diq.fsf@gmail.com>
On Wed, 28 Oct 2026 12:52:30 +0000
"Masalkhi, Abd Alrhman" <abd.masalkhi@gatech.edu> wrote:
> Hi Mariusz,
>
> On Wed, Oct 28, 2026 at 10:03 +0100, Mariusz Tkaczyk wrote:
> > On Thu, 15 Oct 2026 13:03:59 +0000
> > "Masalkhi, Abd Alrhman" <abd.masalkhi@gatech.edu> wrote:
> >
> >> From: Abd-Alrhman Masalkhi <abd.masalkhi@gatech.edu>
> >>
> >> --auto-detect opened md0 (9:0) and issued the RAID_AUTORUN ioctl to
> >> ask the kernel to start the arrays it had auto-detected. The kernel
> >> removed this ioctl in commit d82fa81c2364 ("md: replace the
> >> RAID_AUTORUN ioctl with a direct function call"). Before that, it
> >> worked only when md was built into the kernel. Since then,
> >> md_ioctl()
> >
> > Redhat still builds-in md into kernel so there is chance that
> > someone is using it.
> >
> >
> >> has rejected it with ENOTTY, making --auto-detect ineffective on
> >> current kernels.
> >
> >
> > Hello,
> > Do you mind to submit github PRs for mdadm patches?
> > https://github.com/md-raid-utilities/mdadm
> >
>
> Sure, I will submit the next version as a GitHub pull request.
>
> One question, should I also send the RFC patches for updating mdadm to
> use the new UAPI to the mailing list, or is submitting GitHub PRs
> sufficient?
In this particular case there is nothing interesting we are going to do
with kernel or any problem that needs to be coordinated with kernel.
Just take new UAPI and use it once is available so I don't think kernel
list messaging is needed.
I forgot to say, the problem you are challenging is very legacy. With
proposed change, we will not need to open the device and generate
unnecessary events (and problems) anymore! I'm glad to see someone
working on it.
Mariusz
next prev parent reply other threads:[~2026-10-28 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 13:03 [PATCH] mdadm: Deprecate the obsolete --auto-detect option Masalkhi, Abd Alrhman
2026-10-28 9:03 ` Mariusz Tkaczyk
2026-10-28 12:52 ` Masalkhi, Abd Alrhman
2026-10-28 14:00 ` Mariusz Tkaczyk [this message]
2026-10-28 16:37 ` Masalkhi, Abd Alrhman
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=20261028150047.688d2120@kernel.org \
--to=mtkaczyk@kernel.org \
--cc=abd.masalkhi@gatech.edu \
--cc=blazej.kucman@graidtech.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--cc=yukuai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox