From: syzbot <syzbot+4c882a4a0697c4a25364@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] KASAN: slab-use-after-free Read in handle_mm_fault
Date: Tue, 16 Jul 2024 05:44:01 -0700 [thread overview]
Message-ID: <000000000000422161061d5cb3ee@google.com> (raw)
In-Reply-To: <20240716115504.1136-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+4c882a4a0697c4a25364@syzkaller.appspotmail.com
Tested on:
commit: 3fe121b6 Add linux-next specific files for 20240712
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17749121980000
kernel config: https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
dashboard link: https://syzkaller.appspot.com/bug?extid=4c882a4a0697c4a25364
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11c86045980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-07-16 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 8:29 [syzbot] [crypto?] KASAN: slab-use-after-free Read in handle_mm_fault syzbot
2024-07-16 11:55 ` Hillf Danton
2024-07-16 12:44 ` syzbot [this message]
2024-07-17 2:09 ` Pengfei Xu
2024-07-18 10:59 ` Vlastimil Babka (SUSE)
2024-07-18 15:43 ` Liam R. Howlett
2024-07-18 16:20 ` Suren Baghdasaryan
2024-07-18 16:23 ` Suren Baghdasaryan
2024-07-18 16:36 ` Jason A. Donenfeld
2024-07-18 16:42 ` Suren Baghdasaryan
2024-07-18 16:44 ` Jason A. Donenfeld
2024-07-18 16:49 ` Suren Baghdasaryan
2024-07-18 16:51 ` Jason A. Donenfeld
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=000000000000422161061d5cb3ee@google.com \
--to=syzbot+4c882a4a0697c4a25364@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.