From: syzbot <syzbot+7a9bbb158a7a1071eb27@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jannh@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-usb@vger.kernel.org, pasha.tatashin@soleen.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
yuran.pereira@hotmail.com
Subject: Re: [syzbot] [usb] kernel BUG in __page_table_check_zero
Date: Sun, 20 Oct 2024 11:12:04 -0700 [thread overview]
Message-ID: <671547f4.050a0220.1e4b4d.0049.GAE@google.com> (raw)
In-Reply-To: <000000000000ade4f305fc36868f@google.com>
syzbot suspects this issue was fixed by commit:
commit 79a61cc3fc0466ad2b7b89618a6157785f0293b3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Sep 12 00:11:23 2024 +0000
mm: avoid leaving partial pfn mappings around in error case
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11f76c87980000
start commit: cbf3a2cb156a Merge tag 'nfs-for-6.6-3' of git://git.linux-..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=57da1ac039c4c78a
dashboard link: https://syzkaller.appspot.com/bug?extid=7a9bbb158a7a1071eb27
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15394721680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=152b7af6680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: avoid leaving partial pfn mappings around in error case
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-20 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 16:20 [syzbot] [mm?] " syzbot
2024-10-20 18:12 ` syzbot [this message]
2024-10-20 20:31 ` [syzbot] [usb] " Linus Torvalds
2024-10-21 14:17 ` Jann Horn
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=671547f4.050a0220.1e4b4d.0049.GAE@google.com \
--to=syzbot+7a9bbb158a7a1071eb27@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=yuran.pereira@hotmail.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