From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sparse@vger.kernel.org
Subject: Re: segfault with latest arm64 linux kernel build
Date: Wed, 17 Jun 2026 15:20:14 +0100 [thread overview]
Message-ID: <afe22c99-c4f8-4ade-92ee-c931b57df77e@codethink.co.uk> (raw)
In-Reply-To: <0e0a2543-bac9-41d3-9c06-1579395a1de4@codethink.co.uk>
On 17/06/2026 15:16, Ben Dooks wrote:
> On 17/06/2026 14:58, Ben Dooks wrote:
>> I'm getting a fault running the sparse check on current kernel.
>>
>> CC [M] drivers/gpu/drm/msm/msm_gem.o
>> CHECK /home/ben/linux/drivers/gpu/drm/msm/msm_gem.c
>> Segmentation fault
>>
>> The base of my tree is, however I have a pile of fixes
>> on this:
>>
>> commit 4b99990cdf9560e8a071640baf19f312e6ae02f4 (origin/master,
>> origin/ HEAD)
>> Merge: 9c87e61e3c57 52d4ab1ca790
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>> Date: Wed Jun 17 10:21:00 2026 +0100
>>
>> Merge tag 'drm-next-2026-06-17' of https://
>> gitlab.freedesktop.org/ drm/kernel
>
> I did get a coredump, and the error is at:
>
>> 0 simplify_cgoto (insn=0x7f5fb0ab5240) at simplify.c:2737
>> 2737 if (!target->ep)
>> (gdb) (gdb) backtrace
>> #0 simplify_cgoto (insn=0x7f5fb0ab5240) at simplify.c:2737
>> #1 simplify_instruction (insn=0x7f5fb0ab5240) at simplify.c:2850
>> #2 0x0000563adaef4e30 in clean_up_insns (ep=0x7f5fb0b48198) at
>> optimize.c:42
>> #3 optimize (ep=ep@entry=0x7f5fb0b48198) at optimize.c:98
>> #4 0x0000563adaef49ae in linearize_fn (sym=0x2, base_type=<optimized
>> out>) at linearize.c:2577
>> #5 linearize_symbol (sym=sym@entry=0x7f5fa9cc1b30) at linearize.c:2593
>> #6 0x0000563adaee7c2a in check_symbols (list=<optimized out>) at
>> sparse.c:306
>> #7 0x0000563adaee779d in main (argc=<optimized out>, argv=<optimized
>> out>) at sparse.c:332
>
>
> Not had time to go look into this further
my workaround/fix is:
diff --git a/simplify.c b/simplify.c
index 68c5f9c7..20f5cfc2 100644
--- a/simplify.c
+++ b/simplify.c
@@ -2734,6 +2734,8 @@ static int simplify_cgoto(struct instruction *insn)
break;
case OP_LABEL:
target = def->bb_true;
+ if (!target)
+ return 0;
if (!target->ep)
return 0;
FOR_EACH_PTR(insn->multijmp_list, jmp) {
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2026-06-17 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 13:58 segfault with latest arm64 linux kernel build Ben Dooks
2026-06-17 14:16 ` Ben Dooks
2026-06-17 14:20 ` Ben Dooks [this message]
2026-06-17 14:37 ` Dan Carpenter
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=afe22c99-c4f8-4ade-92ee-c931b57df77e@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sparse@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.