Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sparse@vger.kernel.org
Subject: segfault with latest arm64 linux kernel build
Date: Wed, 17 Jun 2026 14:58:05 +0100	[thread overview]
Message-ID: <ebcf4663-4c95-4b51-887c-d0c99b8b80ea@codethink.co.uk> (raw)

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


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

https://www.codethink.co.uk/privacy.html


             reply	other threads:[~2026-06-17 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 13:58 Ben Dooks [this message]
2026-06-17 14:16 ` segfault with latest arm64 linux kernel build Ben Dooks
2026-06-17 14:20   ` Ben Dooks
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=ebcf4663-4c95-4b51-887c-d0c99b8b80ea@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox