From: syzbot <syzbot+a984066a63e9c1e62662@syzkaller.appspotmail.com>
To: boqun.feng@gmail.com, eadavis@qq.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] INFO: task hung in hci_conn_failed
Date: Wed, 31 Jan 2024 03:29:05 -0800 [thread overview]
Message-ID: <000000000000c041c206103c2f22@google.com> (raw)
In-Reply-To: <20240131102731.1550-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a984066a63e9c1e62662@syzkaller.appspotmail.com
Tested on:
commit: dd85149d rcu/exp: Remove rcu_par_gp_wq
git tree: https://github.com/fbq/linux.git rcu-exp.2024.01.29b
console output: https://syzkaller.appspot.com/x/log.txt?x=1132b337e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9804db253bdfc61
dashboard link: https://syzkaller.appspot.com/bug?extid=a984066a63e9c1e62662
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-01-31 11:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 23:34 [syzbot] [bluetooth?] INFO: task hung in hci_conn_failed syzbot
2024-01-28 1:31 ` Edward Adam Davis
2024-01-28 2:31 ` syzbot
2024-01-29 4:48 ` Hillf Danton
2024-01-29 5:53 ` Tetsuo Handa
2024-01-29 10:47 ` Hillf Danton
2024-01-29 11:28 ` Tetsuo Handa
2024-01-29 20:25 ` Boqun Feng
2024-01-30 11:30 ` Hillf Danton
2024-01-30 15:45 ` syzbot
2024-01-30 23:22 ` Hillf Danton
2024-01-31 6:38 ` Boqun Feng
2024-01-31 10:27 ` Hillf Danton
2024-01-31 11:29 ` syzbot [this message]
2024-01-28 9:15 ` Hillf Danton
2024-01-28 9:41 ` syzbot
2024-01-28 11:28 ` Hillf Danton
2024-01-28 12:06 ` 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=000000000000c041c206103c2f22@google.com \
--to=syzbot+a984066a63e9c1e62662@syzkaller.appspotmail.com \
--cc=boqun.feng@gmail.com \
--cc=eadavis@qq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).