From: syzbot <syzbot+3a0ebe8a52b89c63739d@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] KASAN: slab-use-after-free Read in input_dev_uevent
Date: Tue, 22 Aug 2023 06:49:27 -0700 [thread overview]
Message-ID: <0000000000007706520603834323@google.com> (raw)
In-Reply-To: <20230822115844.2776-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+3a0ebe8a52b89c63739d@syzkaller.appspotmail.com
Tested on:
commit: 7271b2a5 Add linux-next specific files for 20230818
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=145b7ab0680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1936af09cdef7dd6
dashboard link: https://syzkaller.appspot.com/bug?extid=3a0ebe8a52b89c63739d
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11501ecfa80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-08-22 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230822115844.2776-1-hdanton@sina.com>
2023-08-22 13:49 ` syzbot [this message]
2023-08-21 16:48 [syzbot] [input?] KASAN: slab-use-after-free Read in input_dev_uevent syzbot
2023-08-22 9:12 ` Maxime Ripard
2023-08-22 15:57 ` Rahul Rameshbabu
2023-08-22 22:34 ` Rahul Rameshbabu
2023-08-23 7:44 ` Maxime Ripard
2023-08-23 12:51 ` Dmitry Torokhov
2023-08-23 13:16 ` Maxime Ripard
2023-08-23 14:55 ` Dmitry Torokhov
2023-08-23 16:30 ` Maxime Ripard
2023-08-23 17:04 ` Rahul Rameshbabu
2023-08-23 17:56 ` Dmitry Torokhov
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=0000000000007706520603834323@google.com \
--to=syzbot+3a0ebe8a52b89c63739d@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.