From: syzbot <syzbot+8e41bb0c055b209ebbf4@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in input_register_device (2)
Date: Thu, 08 Feb 2024 01:36:04 -0800 [thread overview]
Message-ID: <00000000000052d5570610db8a2d@google.com> (raw)
In-Reply-To: <tencent_E9DD8E5D8799084FFF8DBA25EC0D84921407@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+8e41bb0c055b209ebbf4@syzkaller.appspotmail.com
Tested on:
commit: 04737196 Merge tag 'v6.8-p3' of git://git.kernel.org/p..
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=13ab9118180000
kernel config: https://syzkaller.appspot.com/x/.config?x=a569be813824c2a8
dashboard link: https://syzkaller.appspot.com/bug?extid=8e41bb0c055b209ebbf4
compiler: riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: riscv64
patch: https://syzkaller.appspot.com/x/patch.diff?x=12fc85d4180000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-02-08 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 19:54 [syzbot] [input?] [usb?] WARNING in input_register_device (2) syzbot
2024-02-08 8:56 ` Edward Adam Davis
2024-02-08 9:36 ` syzbot [this message]
2024-02-08 10:46 ` [PATCH riscv64] kobject: fix WARNING in input_register_device Edward Adam Davis
2024-02-08 10:56 ` Greg KH
2024-02-08 11:37 ` Edward Adam Davis
2024-02-08 12:25 ` Greg KH
2024-02-13 0:43 ` Edward Adam Davis
2024-02-13 7:20 ` Greg KH
2024-02-13 13:10 ` Edward Adam Davis
2024-02-08 12:25 ` Greg KH
2024-02-13 0:50 ` Edward Adam Davis
2024-02-13 7:21 ` Greg KH
2024-02-13 13:13 ` Edward Adam Davis
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=00000000000052d5570610db8a2d@google.com \
--to=syzbot+8e41bb0c055b209ebbf4@syzkaller.appspotmail.com \
--cc=eadavis@qq.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.