From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernelci@lists.linux.dev
Cc: kernelci-results@groups.io, gus@collabora.com,
linux-rt-devel@lists.linux.dev
Subject: Re: [REGRESSION] stable-rt/v6.1-rt-next: (build) ./include/net/ip.h:456:14: error: default initialization of an obj...
Date: Tue, 25 Nov 2025 08:19:52 +0100 [thread overview]
Message-ID: <20251125071952.lq2vP2n8@linutronix.de> (raw)
In-Reply-To: <176403954885.358.6925837698022425297@f771fd7c9232>
On 2025-11-25 02:59:09 [-0000], KernelCI bot wrote:
> Hello,
Hi,
> New build issue found on stable-rt/v6.1-rt-next:
Thank you.
> ---
> ./include/net/ip.h:456:14: error: default initialization of an object of type 'typeof (rt->dst.expires)' (aka 'const unsigned long') leaves the object uninitialized [-Werror,-Wdefault-const-init-var-unsafe] in security/selinux/avc.o (security/selinux/avc.c) [logspec:kbuild,kbuild.compiler.error]
> ---
>
> - dashboard: https://d.kernelci.org/i/maestro:dabc8a89dbfbb7a418c712c2c6c82e29bd2c9573
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> - commit HEAD: 14fd3f12318030025dddcaf840092144c3a99e89
> - tags: v6.1.46-rt14-rc1
This one has been "fixed" by commit d0afcfeb9e381 ("kbuild: Disable
-Wdefault-const-init-unsafe"). It is also part of v6.1.141-rt52 and
later.
…
> This is an experimental report format. Please send feedback in!
> Talk to us at kernelci@lists.linux.dev
For RT, or kernels in general, it should be enough to test the last
kernel/ tag from each release branch. The older ones, such at as this
one, may contain bugs which will not be fixed in "this" release but a
subsequent release may contains a fix if possible.
Sebastian
parent reply other threads:[~2025-11-25 7:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <176403954885.358.6925837698022425297@f771fd7c9232>]
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=20251125071952.lq2vP2n8@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-rt-devel@lists.linux.dev \
/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