From: syzbot <syzbot+89edd67979b52675ddec@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com, jannh@google.com,
jose.pekkarinen@foxhound.fi, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in __pte_offset_map_lock
Date: Thu, 16 Nov 2023 22:24:05 -0800 [thread overview]
Message-ID: <000000000000e78e3e060a532ee7@google.com> (raw)
In-Reply-To: <180788a2-b714-ebf3-962c-8aabdeff0c45@google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+89edd67979b52675ddec@syzkaller.appspotmail.com
Tested on:
commit: b85ea95d Linux 6.7-rc1
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14e7e350e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fffc11e84313b7c6
dashboard link: https://syzkaller.appspot.com/bug?extid=89edd67979b52675ddec
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1586ca14e80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-11-17 6:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:48 [syzbot] [mm?] BUG: unable to handle kernel paging request in __pte_offset_map_lock syzbot
2023-10-27 6:07 ` Hugh Dickins
2023-10-27 6:07 ` Hugh Dickins
2023-11-15 19:39 ` Matthew Wilcox
2023-11-15 19:39 ` Matthew Wilcox
2023-11-14 11:30 ` [syzbot] " syzbot
2023-11-14 11:47 ` syzbot
2023-11-14 15:43 ` syzbot
2023-11-14 17:10 ` syzbot
2023-11-14 18:25 ` syzbot
2023-11-16 7:39 ` [syzbot] [mm?] " Hugh Dickins
2023-11-16 7:59 ` syzbot
2023-11-17 5:42 ` Hugh Dickins
2023-11-17 6:24 ` syzbot [this message]
[not found] <306c9c271642326cb02d59447b6fb4d6@foxhound.fi>
2023-11-14 11:57 ` syzbot
[not found] <82909cf60e85b216c14be8fa3ef036f0@foxhound.fi>
2023-11-14 12:16 ` syzbot
[not found] <58662b6bdb914d8c6411d0994e791d53@foxhound.fi>
2023-11-14 16:11 ` syzbot
[not found] <674a0d1a2b541f6d3c199b5bddda8db9@foxhound.fi>
2023-11-14 17:38 ` syzbot
[not found] <aa2ae5537093181aac903a420c029113@foxhound.fi>
2023-11-14 18:49 ` syzbot
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=000000000000e78e3e060a532ee7@google.com \
--to=syzbot+89edd67979b52675ddec@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jose.pekkarinen@foxhound.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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.