Re: [PATCH] init/main.c: prevent warning on lack of default implicit rdinit

[Andrew Morton <akpm@linux-foundation.org>]

On Thu, 15 Jan 2026 23:09:07 +0000 Harry Austen <hpausten@protonmail.com> wrote:

> On Thursday, 15 January 2026 at 20:02, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > 
> > 
> > On Wed, 14 Jan 2026 22:02:27 +0000 Harry Austen hpausten@protonmail.com wrote:
> > 
> > > If rdinit was not explicitly provided on cmdline, and default /init does
> > > not exist, no warning should be printed.
> > 
> > 
> > Seems that we already have a very similar patch from Lillian:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/init-mainc-check-if-rdinit-was-explicitly-set-before-printing-warning.patch
> > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/init-mainc-check-if-rdinit-was-explicitly-set-before-printing-warning-fix.patch
> > 
> > What's happening here?
> 
> Oh, interesting. Have those already been accepted?

They're in the mm.git queue for the next merge window.  As such they
are subject to test/review/alteration/dropping/etc.

> Looks like there's no
> additional ENOENT check, so the warning gets printed even less often, which is fine by me.
> 
> Apologies for missing that this appears to have already been fixed and feel free
> to ignore my patch.

OK, no probs, thanks, please send along any alterations to Lillian's
patch if you see a need.  linux-next would be a suitable base for
that.