From: dan@danm.net
To: toralf.foerster@gmx.de
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: 6.5.13 regression: BUG: kernel NULL pointer dereference, address: 0000000000000020
Date: Tue, 28 Nov 2023 14:30:18 -0700 [thread overview]
Message-ID: <20231128213018.6896-1-dan@danm.net> (raw)
In-Reply-To: <2b5d6cd4-0afb-4193-ab88-235f910a7293@gmx.de>
I'm seeing this too, but on 6.6.3 (6.6.2 is fine).
Bisected it down to commit 2e8b4e0992e16 ("gcc-plugins: randstruct:
Only warn about true flexible arrays"). Reverting that commit on top
of v6.6.3 makes it go away.
I do wonder if content such as that (which *looks* like it's purely
preparing for future changes) is appropriate for the stable trees.
Cheers,
-- Dan
next parent reply other threads:[~2023-11-28 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2b5d6cd4-0afb-4193-ab88-235f910a7293@gmx.de>
2023-11-28 21:30 ` dan [this message]
2023-11-28 21:42 ` 6.5.13 regression: BUG: kernel NULL pointer dereference, address: 0000000000000020 Sam James
2023-11-28 22:48 ` Dan Moulding
2023-11-29 18:59 ` Gustavo A. R. Silva
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=20231128213018.6896-1-dan@danm.net \
--to=dan@danm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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