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]

Message-ID: <ZAbfvyH5pSAVdX8K@kroah.com>
Date:   Tue, 7 Mar 2023 07:54:55 +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 07:31:57AM +0100, Greg KH 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...

Oh nevermind, this is my fault, the patch is buggy, let me fix it up,
sorry for the noise...

greg k-h