linux-kernel - Re: linux-next: runtime warning after merge of the driver-core tree

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 7 Mar 2023 09:01:56 +0100
From:   Greg KH <greg@...ah.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: runtime warning after merge of the driver-core tree

On Tue, Mar 07, 2023 at 05:48:55PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Tue, 7 Mar 2023 07:31:57 +0100 Greg KH <greg@...ah.com> wrote:
> >
> > On Tue, Mar 07, 2023 at 01:43:13PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > After merging the driver-core tree, today's linux-next qemu boot
> > > (powerpc pseries_le_defconfig) produced this boot time warning:
> > > 
> > > HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
> > > sysfs: cannot create duplicate filename '//block'  
> > 
> > That is odd.  What type of userspace are you running this with?  And is
> > there a pointer to the .config anywhere?  No one should be needing this
> > old config option anymore, but maybe I messed something up in removing
> > it...
> The userspace is a trivial PowerPC LE initramfs that just shuts down
> after it boots.  However, the warning occurs before the initramfs is
> even unpacked.
> 
> I have attached the generated .config

No .config was attached :(

Anyway, should now be fixed with:
	https://lore.kernel.org/r/20230307075102.3537-1-gregkh@linuxfoundation.org

I'll queue that up to my tree so hopefully linux-next will be working
properly tomorrow.  Sorry for the bug.

greg k-h