From: syzbot <syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_exists
Date: Fri, 31 Mar 2023 02:18:26 -0700 [thread overview]
Message-ID: <0000000000000db75105f82eb1b7@google.com> (raw)
In-Reply-To: <20230331084907.3220-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com
Tested on:
commit: a6d9e303 Add linux-next specific files for 20230330
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=134609cdc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=aceb117f7924508e
dashboard link: https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=133a6835c80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-03-31 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230331084907.3220-1-hdanton@sina.com>
2023-03-31 9:18 ` syzbot [this message]
[not found] <20230331080108.3156-1-hdanton@sina.com>
2023-03-31 8:16 ` [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_exists syzbot
[not found] <20230331032008.3067-1-hdanton@sina.com>
2023-03-31 3:37 ` syzbot
2023-01-20 16:28 [syzbot] " syzbot
2023-03-31 0:21 ` [syzbot] [bluetooth?] " syzbot
2024-11-17 14:03 ` 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=0000000000000db75105f82eb1b7@google.com \
--to=syzbot+b69a625d06e8ece26415@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.