From: syzbot <syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com>
To: code@siddh.me, hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in post_one_notification
Date: Mon, 01 Aug 2022 03:54:09 -0700 [thread overview]
Message-ID: <000000000000c7a83905e52bd127@google.com> (raw)
In-Reply-To: <20220801103533.972-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com
Tested on:
commit: 3d7cb6b0 Linux 5.19
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14066d7a080000
kernel config: https://syzkaller.appspot.com/x/.config?x=70dd99d568a89e0
dashboard link: https://syzkaller.appspot.com/bug?extid=c70d87ac1d001f29a058
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-08-01 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220801103533.972-1-hdanton@sina.com>
2022-08-01 10:54 ` syzbot [this message]
2022-08-02 22:27 ` [syzbot] KASAN: use-after-free Read in post_one_notification Eric Biggers
2022-08-03 4:04 ` Siddh Raman Pant
2022-08-03 4:09 ` Eric Biggers
2022-08-03 5:17 ` Siddh Raman Pant
[not found] <20220723142031.2316-1-hdanton@sina.com>
2022-07-23 14:39 ` syzbot
2022-03-21 13:25 syzbot
2022-03-21 15:40 ` David Howells
2022-03-22 7:52 ` Dmitry Vyukov
2022-07-23 13:20 ` Siddh Raman Pant
2022-07-23 13:21 ` syzbot
2022-07-23 13:22 ` Siddh Raman Pant
2022-07-23 13:42 ` syzbot
2022-07-24 3:41 ` Siddh Raman Pant
2022-07-24 4:01 ` syzbot
2022-07-28 15:30 ` Siddh Raman Pant
2022-07-28 15:50 ` 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=000000000000c7a83905e52bd127@google.com \
--to=syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com \
--cc=code@siddh.me \
--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.