From: syzbot <syzbot+685e14d04fe35692d3bc@syzkaller.appspotmail.com>
To: eadavis@qq.com, gregkh@linuxfoundation.org, keithp@keithp.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] possible deadlock in chaoskey_release
Date: Wed, 09 Oct 2024 06:59:03 -0700 [thread overview]
Message-ID: <67068c27.050a0220.1139e6.0000.GAE@google.com> (raw)
In-Reply-To: <tencent_3212D5C64009A62EE86ED08C8467FD46D606@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+685e14d04fe35692d3bc@syzkaller.appspotmail.com
Tested-by: syzbot+685e14d04fe35692d3bc@syzkaller.appspotmail.com
Tested on:
commit: 4a9fe2a8 dt-bindings: usb: dwc3-imx8mp: add compatible..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=115fbf9f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4510af5d637450fb
dashboard link: https://syzkaller.appspot.com/bug?extid=685e14d04fe35692d3bc
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=105e1327980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-10-09 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 3:33 [syzbot] [usb?] possible deadlock in chaoskey_release syzbot
2024-10-09 8:43 ` [usb?] possible deadlock in chaoskey_open Edward Adam Davis
2024-10-09 13:59 ` syzbot [this message]
2024-10-09 14:52 ` [PATCH next] USB: chaoskey: Fix possible deadlock chaoskey_list_lock 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=67068c27.050a0220.1139e6.0000.GAE@google.com \
--to=syzbot+685e14d04fe35692d3bc@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=gregkh@linuxfoundation.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox