All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Sasha Levin <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Chuck Lever <cel@kernel.org>
Subject: Re: queue/5.15 kernel build failure
Date: Mon, 18 Aug 2025 07:52:06 +0200	[thread overview]
Message-ID: <2025081837-rascal-unsafe-d1e1@gregkh> (raw)
In-Reply-To: <caef2fc2-8e80-4fc8-9e88-f5d030542534@oracle.com>

On Sun, Aug 17, 2025 at 04:05:18PM -0400, Chuck Lever wrote:
> On 8/17/25 4:02 PM, Sasha Levin wrote:
> > On Sun, Aug 17, 2025 at 01:11:14PM -0400, Chuck Lever wrote:
> >> Hi-
> >>
> >> Building on RHEL 9.6, I encountered this build failure:
> >>
> >> arch/x86/kernel/smp.o: warning: objtool: fred_sysvec_reboot()+0x52:
> >> unreachable instruction
> >> drivers/gpu/drm/vmwgfx/vmwgfx_msg.o: warning: objtool:
> >> vmw_port_hb_out()+0xbf: stack state mismatch: cfa1=5+16 cfa2=4+8
> >> drivers/gpu/drm/vmwgfx/vmwgfx_msg.o: warning: objtool:
> >> vmw_port_hb_in()+0xb4: stack state mismatch: cfa1=5+16 cfa2=4+8
> >> drivers/vfio/vfio_iommu_type1.c: In function ‘vfio_pin_pages_remote’:
> >> drivers/vfio/vfio_iommu_type1.c:707:25: error: ISO C90 forbids mixed
> >> declarations and code [-Werror=declaration-after-statement]
> >>  707 |                         long req_pages = min_t(long, npage,
> >> batch->capacity);
> >>      |                         ^~~~
> >> cc1: all warnings being treated as errors
> >> gmake[2]: *** [scripts/Makefile.build:289:
> >> drivers/vfio/vfio_iommu_type1.o] Error 1
> >> gmake[1]: *** [scripts/Makefile.build:552: drivers/vfio] Error 2
> >> gmake[1]: *** Waiting for unfinished jobs....
> >> gmake: *** [Makefile:1926: drivers] Error 2
> >>
> >> Appears to be due to:
> >>
> >> commit 5c87f3aff907e72fa6759c9dc66eb609dec1815c
> > 
> > I've dropped this, thanks for the report.
> > 
> > It's a bit funny - my version of gcc treats it as a warning, and it
> > actually
> > gives me quite a few mote "mixed decrlataions" warnings in the 5.15
> > allmodconfig build.
> > 
> > Compilers are hard :)
> > 
> 
> Additional context: I copied the RHEL 9.6 /boot/config to do the build.
> I think Red Hat likes to keep the "treat warnings as errors" setting
> enabled in their builds.

It's a good warning to have, 'allmodconfig' enables it, and so my builds
show these as failures too, so you aren't alone.

thanks for pointing it out.

greg k-h

      reply	other threads:[~2025-08-18  5:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 17:11 queue/5.15 kernel build failure Chuck Lever
2025-08-17 20:02 ` Sasha Levin
2025-08-17 20:05   ` Chuck Lever
2025-08-18  5:52     ` Greg KH [this message]

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=2025081837-rascal-unsafe-d1e1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=sashal@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.