From: Roman Gushchin <roman.gushchin@linux.dev>
To: Erhard Furtner <erhard_f@mailbox.org>
Cc: linux-mm@kvack.org
Subject: Re: [bisected] clang 16 built kernel crashes w. "BUG: kernel NULL pointer dereference, address: 00000007", gcc 13 built kernel with same config boots fine (6.7-rc1, x86_32)
Date: Wed, 15 Nov 2023 19:00:06 -0800 [thread overview]
Message-ID: <ZVWFth-swkYbwK25@P9FQF9L96D.corp.robot.car> (raw)
In-Reply-To: <20231115234648.4eb10131@yea>
On Wed, Nov 15, 2023 at 11:46:48PM +0100, Erhard Furtner wrote:
> On Wed, 15 Nov 2023 09:33:17 -0800
> Roman Gushchin <roman.gushchin@linux.dev> wrote:
>
> > Hm, interesting, so the issue is happening only with a kernel built with clang-16
> > but not gcc? And you use 32-bit kernel? Do you know if it's reproducible on a
> > 64-bit machine?
>
> Correct. This only happens when I build the kernel with clang-16. A gcc-13 kernel build using the same .config is fine. That's why I reported it first on https://github.com/ClangBuiltLinux/linux/issues/1959
>
> Surprisingly I was indeed able to reproduce the issue on my amd64 box!
Ok, I reproduced it too, mastered a fix and sent upstream (you're cc'ed and also
mentioned in the commit message). Luckily the problem is trivial, as is the fix.
I expect Andrew to pick it up soon, but don't be surprised with some delay - it's
a Linux Plumbers week.
Thank you for the detailed report and your help with the reproduction of the problem!
prev parent reply other threads:[~2023-11-16 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 0:15 Erhard Furtner
2023-11-15 17:33 ` Roman Gushchin
2023-11-15 22:46 ` Erhard Furtner
2023-11-16 3:00 ` Roman Gushchin [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=ZVWFth-swkYbwK25@P9FQF9L96D.corp.robot.car \
--to=roman.gushchin@linux.dev \
--cc=erhard_f@mailbox.org \
--cc=linux-mm@kvack.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