From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: syzbot <syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, bigeasy@linutronix.de,
dwmw2@infradead.org, dwmw@amazon.co.uk, kvm@vger.kernel.org,
liam.howlett@oracle.com, liam@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-rt-devel@lists.linux.dev, lkp@intel.com,
llvm@lists.linux.dev, lorenzo.stoakes@oracle.com,
me@brighamcampbell.com, mhocko@suse.com, nogikh@google.com,
oe-kbuild-all@lists.linux.dev, pbonzini@redhat.com,
rientjes@google.com, rppt@kernel.org, seanjc@google.com,
shaikhkamal2012@gmail.com, shakeel.butt@linux.dev,
skhan@linuxfoundation.org, surenb@google.com,
syzkaller-bugs@googlegroups.com, vbabka@kernel.org
Subject: Re: [syzbot] [kvm?] BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
Date: Thu, 17 Sep 2026 08:51:15 +0100 [thread overview]
Message-ID: <aqubuvR_2XCNav28@gremlin> (raw)
In-Reply-To: <6aaaecd6.4e05fbd6.392abc.0003.GAE@google.com>
On Wed, Sep 16, 2026 at 12:24:06PM -0700, syzbot wrote:
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
>
> failed to apply patch:
> error: corrupt patch at line 7
OK let's try again, aping
https://lore.kernel.org/all/b434f7828a4d7b24de76aa5609dadda2871a932a.camel@infradead.org/
as I see this branch is still there (David W - I hope this is OK! :)
#syz test git://git.infradead.org/users/dwmw2/linux.git seb-nonblock-rt-test
>
>
>
> Tested on:
>
> commit: 9b87fdc9 Merge tag 'sched_ext-for-7.3-rc3-fixes' of gi..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=b454dc6b1b7acd30
> dashboard link: https://syzkaller.appspot.com/bug?extid=c3178b6b512446632bac
> compiler:
> patch: https://syzkaller.appspot.com/x/patch.diff?x=15a16bf9580000
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-09-17 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 7:41 [syzbot] [mm?] BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start syzbot
2026-05-04 17:54 ` syzbot
2026-05-06 13:57 ` Sean Christopherson
2026-08-21 12:09 ` Forwarded: " syzbot
2026-08-25 12:38 ` Forwarded: Re: [syzbot] [kernel?] " syzbot
2026-09-16 14:08 ` [syzbot] [kvm?] " syzbot
2026-09-16 18:05 ` Lorenzo Stoakes (ARM)
2026-09-16 19:24 ` syzbot
2026-09-17 7:51 ` Lorenzo Stoakes (ARM) [this message]
2026-09-17 8:25 ` syzbot
2026-09-17 7:39 ` Sebastian Andrzej Siewior
2026-09-17 7:49 ` Lorenzo Stoakes (ARM)
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=aqubuvR_2XCNav28@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=liam.howlett@oracle.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=me@brighamcampbell.com \
--cc=mhocko@suse.com \
--cc=nogikh@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shaikhkamal2012@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@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.