lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260115152857.12f32b47493d61d9948afd85@linux-foundation.org>
Date: Thu, 15 Jan 2026 15:28:57 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Harry Austen <hpausten@...tonmail.com>
Cc: Huacai Chen <chenhuacai@...nel.org>, linux-kernel@...r.kernel.org,
 Lillian Berry <lillian@...r-ark.net>
Subject: Re: [PATCH] init/main.c: prevent warning on lack of default
 implicit rdinit

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

> On Thursday, 15 January 2026 at 20:02, Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > 
> > 
> > On Wed, 14 Jan 2026 22:02:27 +0000 Harry Austen hpausten@...tonmail.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.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ