public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: runtime warning after merge of the driver-core tree
Date: Tue, 7 Mar 2023 22:51:19 +1100	[thread overview]
Message-ID: <20230307225119.6c3e257c@canb.auug.org.au> (raw)
In-Reply-To: <ZAbvdBbavVDnlgnJ@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]

Hi Greg,

On Tue, 7 Mar 2023 09:01:56 +0100 Greg KH <greg@kroah.com> wrote:
>
> 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@kroah.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 :(

Yeah, sorry, by the time I noticed you had posted that you thought you
knew what the problem was, so I didn't bother sending it.

> 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.

OK, thanks.  I will let you know if it still warns ;-)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-03-07 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  2:43 linux-next: runtime warning after merge of the driver-core tree Stephen Rothwell
2023-03-07  6:31 ` Greg KH
2023-03-07  6:48   ` Stephen Rothwell
2023-03-07  8:01     ` Greg KH
2023-03-07 11:51       ` Stephen Rothwell [this message]
2023-03-07  6:54   ` Greg KH

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=20230307225119.6c3e257c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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