From: syzbot <syzbot+5759bce381cb6f9c51fa@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com,
apopple@nvidia.com, arnd@arndb.de, bgray@linux.ibm.com,
bp@alien8.de, catalin.marinas@arm.com,
christophe.leroy@csgroup.eu, dave.hansen@linux.intel.com,
hpa@zytor.com, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, luto@kernel.org,
mingo@redhat.com, mpe@ellerman.id.au, npiggin@gmail.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, will@kernel.org, x86@kernel.org
Subject: Re: [syzbot] [kernel?] general protection fault in arch_tlbbatch_flush
Date: Mon, 11 Sep 2023 18:34:35 -0700 [thread overview]
Message-ID: <00000000000007e38806051f72e2@google.com> (raw)
In-Reply-To: <0000000000003afcb4060135a664@google.com>
syzbot has bisected this issue to:
commit 75c400f82d347af1307010a3e06f3aa5d831d995
Author: Alistair Popple <apopple@nvidia.com>
Date: Wed Jul 19 12:18:44 2023 +0000
mmu_notifiers: call invalidate_range() when invalidating TLBs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14bd6d0c680000
start commit: c58c49dd8932 Add linux-next specific files for 20230720
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16bd6d0c680000
console output: https://syzkaller.appspot.com/x/log.txt?x=12bd6d0c680000
kernel config: https://syzkaller.appspot.com/x/.config?x=27d64413bce3a1d8
dashboard link: https://syzkaller.appspot.com/bug?extid=5759bce381cb6f9c51fa
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177f484ea80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e4a4e6a80000
Reported-by: syzbot+5759bce381cb6f9c51fa@syzkaller.appspotmail.com
Fixes: 75c400f82d34 ("mmu_notifiers: call invalidate_range() when invalidating TLBs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2023-09-12 1:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000003afcb4060135a664@google.com>]
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=00000000000007e38806051f72e2@google.com \
--to=syzbot+5759bce381cb6f9c51fa@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=arnd@arndb.de \
--cc=bgray@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).