From: syzbot <syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, dwmw2@infradead.org,
linux-kernel@vger.kernel.org, nogikh@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
Date: Tue, 25 Aug 2026 06:37:02 -0700 [thread overview]
Message-ID: <6a8d9a7e.a5a502ce.31d34.0069.GAE@google.com> (raw)
In-Reply-To: <b434f7828a4d7b24de76aa5609dadda2871a932a.camel@infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com
Tested-by: syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com
Tested on:
commit: f902e69c sched: Allow sleeping spinlocks on PREEMPT_RT..
git tree: git://git.infradead.org/users/dwmw2/linux.git seb-nonblock-rt-test
console output: https://syzkaller.appspot.com/x/log.txt?x=12f76625580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a263b38e64491d5
dashboard link: https://syzkaller.appspot.com/bug?extid=c3178b6b512446632bac
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-25 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe3076ef2e0b6fbb330bee69650718138d61b0fa.camel@infradead.org>
2026-08-25 12:50 ` syzbot
2026-08-25 12:56 ` Aleksandr Nogikh
2026-08-25 13:10 ` David Woodhouse
2026-08-25 13:37 ` syzbot [this message]
[not found] <d4c5e3f93eeb4f60bb5c826b9ae81f85c8ccf256.camel@infradead.org>
2026-08-21 12:43 ` syzbot
2025-12-08 7:41 syzbot
2026-05-04 17:54 ` syzbot
2026-05-06 13:57 ` Sean Christopherson
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=6a8d9a7e.a5a502ce.31d34.0069.GAE@google.com \
--to=syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzkaller-bugs@googlegroups.com \
/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®