From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Dan Moulding <dan@danm.net>, sam@gentoo.org
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, toralf.foerster@gmx.de
Subject: Re: 6.5.13 regression: BUG: kernel NULL pointer dereference, address: 0000000000000020
Date: Wed, 29 Nov 2023 12:59:19 -0600 [thread overview]
Message-ID: <a4890aae-2be8-42e3-9aa1-ee62f892553f@embeddedor.com> (raw)
In-Reply-To: <20231128224816.6563-1-dan@danm.net>
> the kernel source. But a quick (and possibly imperfect) grepping seems
> to show that struct neighbor was the only one used with
> __randomize_layout. So, I *think* it might be the only one that could
> cause a problem with the recent change to the randomize_layout plugin.
Yeah, I can confirm we don't currently have any other fake flex array
in a struct with __randomize_layout. :)
--
Gustavo
prev parent reply other threads:[~2023-11-29 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 20:29 Toralf Förster
2023-11-28 21:30 ` dan
2023-11-28 21:42 ` Sam James
2023-11-28 22:48 ` Dan Moulding
2023-11-29 18:59 ` Gustavo A. R. Silva [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=a4890aae-2be8-42e3-9aa1-ee62f892553f@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=dan@danm.net \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@gentoo.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
all inboxes | Powered by JetHome®