mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+6cdbd5e494b199d820c3@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	senozhatsky@chromium.org, syzkaller-bugs@googlegroups.com,
	tglx@kernel.org, tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [kernel?] WARNING in do_clear_cpu_cap
Date: Fri, 31 Jul 2026 10:35:26 -0700	[thread overview]
Message-ID: <20260731103526.9b9c02f8b5a95b190b23ee51@linux-foundation.org> (raw)
In-Reply-To: <6a6cd7be.1aa927e4.17d4bf.0005.GAE@google.com>

On Fri, 31 Jul 2026 10:13:34 -0700 syzbot <syzbot+6cdbd5e494b199d820c3@syzkaller.appspotmail.com> wrote:

> syzbot found the following issue on:
> 
> HEAD commit:    11028ab62899 Merge tag 'probes-fixes-v7.2-rc5' of git://gi..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=14e3d9b9580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=cb17729fb04b1e3a
> dashboard link: https://syzkaller.appspot.com/bug?extid=6cdbd5e494b199d820c3
> compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13b271b9580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=118a97b1580000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/bc967be819a3/disk-11028ab6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/6e9f003c9cc8/vmlinux-11028ab6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/5c292926486f/bzImage-11028ab6.xz
> 
> The issue was bisected to:
> 
> commit 684826f8271ad97580b138b9ffd462005e470b99
> Author: Sergey Senozhatsky <senozhatsky@chromium.org>
> Date:   Wed Sep 11 02:54:56 2024 +0000
> 
>     zram: free secondary algorithms names

Thanks.  I don't see how zram could have caused this.

fwiw (which might not be a lot), Gemini concluded


Core Issue & Summary

  Root Cause: CPU capability clearing (clear_cpu_cap /
  setup_clear_cpu_cap) was executed during late CPU feature detection
  on a secondary core (identify_secondary_cpu()) after kernel
  alternatives patching was finalized (alternatives_patched == true).

Fix Location:

  The bug needs to be addressed in arch/x86/kernel/cpu/intel.c
  (specifically around early_init_intel()) by ensuring that capability
  overrides/clears are done prior to alternative patching or handled
  via per-CPU feature suppression mechanisms that don't invoke full
  feature mask clearing post-patching.

https://gemini.google.com/share/0cdd1930799f?skid=006fb41e-8e42-4330-9f52-62c4cf089ce0

  reply	other threads:[~2026-07-31 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 17:13 syzbot
2026-07-31 17:35 ` Andrew Morton [this message]
2026-07-31 18:22   ` Borislav Petkov

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=20260731103526.9b9c02f8b5a95b190b23ee51@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=senozhatsky@chromium.org \
    --cc=syzbot+6cdbd5e494b199d820c3@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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

all inboxes | Powered by JetHome®