From: syzbot <syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4)
Date: Fri, 01 Dec 2023 21:14:05 -0800 [thread overview]
Message-ID: <000000000000329bb5060b7ff438@google.com> (raw)
In-Reply-To: <tencent_75CC257BBAC7BBA6337C9E541B054BF91B08@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com
Tested on:
commit: 8c9660f6 Add linux-next specific files for 20231124
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=125ebdaae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6eff11e3e3c25a4f
dashboard link: https://syzkaller.appspot.com/bug?extid=ed812ed461471ab17a0c
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=11cd5352e80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-12-02 5:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_75CC257BBAC7BBA6337C9E541B054BF91B08@qq.com>
2023-12-02 5:14 ` syzbot [this message]
[not found] <tencent_3436E64AC8741F77C766E83DE336CA963209@qq.com>
2023-12-02 3:36 ` [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) syzbot
[not found] <tencent_E68094D8E9BAEFDACCF878BA6C342CE16E0A@qq.com>
2023-12-02 2:33 ` syzbot
[not found] <tencent_2C6C333F9ED41B104B521B6E25D8BA6BBB08@qq.com>
2023-12-02 1:47 ` syzbot
2023-11-30 21:17 syzbot
2023-12-01 8:29 ` Pengfei Xu
2024-10-11 19:20 ` Jens Axboe
2024-10-11 19:32 ` Aleksandr Nogikh
2024-10-11 19:33 ` Jens Axboe
2024-10-11 19:41 ` Aleksandr Nogikh
2024-10-11 20:43 ` Jens Axboe
2024-10-14 7:58 ` Aleksandr Nogikh
2024-10-12 1:20 ` 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=000000000000329bb5060b7ff438@google.com \
--to=syzbot+ed812ed461471ab17a0c@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.