All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2f32bc207cbe5ca4b7a2@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-kernel@vger.kernel.org, luto@kernel.org, mingo@kernel.org,
	 mingo@redhat.com, peterz@infradead.org, riel@surriel.com,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	x86@kernel.org
Subject: Re: [syzbot] [kernel?] WARNING in flush_tlb_func
Date: Wed, 11 Dec 2024 03:17:05 -0800	[thread overview]
Message-ID: <675974b1.050a0220.1ac542.0009.GAE@google.com> (raw)
In-Reply-To: <67436e63.050a0220.1cc393.0048.GAE@google.com>

syzbot has bisected this issue to:

commit 209954cbc7d0ce1a190fc725d20ce303d74d2680
Author: Rik van Riel <riel@surriel.com>
Date:   Thu Nov 14 15:26:16 2024 +0000

    x86/mm/tlb: Update mm_cpumask lazily

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13b9b3e8580000
start commit:   f486c8aa16b8 Add linux-next specific files for 20241128
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1079b3e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17b9b3e8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
dashboard link: https://syzkaller.appspot.com/bug?extid=2f32bc207cbe5ca4b7a2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17c16fc0580000

Reported-by: syzbot+2f32bc207cbe5ca4b7a2@syzkaller.appspotmail.com
Fixes: 209954cbc7d0 ("x86/mm/tlb: Update mm_cpumask lazily")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-12-11 11:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 18:20 [syzbot] [kernel?] WARNING in flush_tlb_func syzbot
2024-12-03 13:08 ` syzbot
2024-12-11 11:17 ` syzbot [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=675974b1.050a0220.1ac542.0009.GAE@google.com \
    --to=syzbot+2f32bc207cbe5ca4b7a2@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --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 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.