From: Jens Axboe <axboe@kernel.dk>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.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, 11 Oct 2024 13:33:57 -0600 [thread overview]
Message-ID: <4661f4ef-44a0-402b-864b-83ef8d31f07e@kernel.dk> (raw)
In-Reply-To: <CANp29Y6Zvqt7K9_LWEPQ4X-n1WOJbN0W83wx7a6GRhRFuX_OLw@mail.gmail.com>
On 10/11/24 1:32 PM, Aleksandr Nogikh wrote:
> (minus most people and mailing lists)
>
> On Fri, Oct 11, 2024 at 9:20 PM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> On Thu, Nov 30, 2023 at 2:17?PM syzbot <syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com> wrote:
>>>
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit: 8c9660f65153 Add linux-next specific files for 20231124
>>> git tree: linux-next
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=1006f178e80000
>>> kernel config: https://syzkaller.appspot.com/x/.config?x=ca1e8655505e280
>>> 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
>>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ec6e62e80000
>>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11964f7ce80000
>>
>> syz test: git://git.kernel.dk/linux btrace-fault
>
> It should begin with a # :)
>
> #syz test: git://git.kernel.dk/linux btrace-fault
hah thanks, I always have to click the link to remember what to type.
Guess even with that I messed it up...
--
Jens Axboe
next prev parent reply other threads:[~2024-10-11 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:17 [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) syzbot
2023-12-01 8:29 ` Pengfei Xu
2023-12-02 1:25 ` [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl syzbot
2023-12-02 2:14 ` syzbot
2023-12-02 2:44 ` syzbot
2023-12-02 2:54 ` syzbot
[not found] ` <tencent_6537E04AAC74F976B567603CEB377A96FA09@qq.com>
2023-12-02 9:19 ` [PATCH next] trace/blktrace: fix " Yu Kuai
2023-12-02 22:07 ` Steven Rostedt
2023-12-03 11:45 ` Pengfei Xu
2024-10-11 19:20 ` [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) Jens Axboe
2024-10-11 19:32 ` Aleksandr Nogikh
2024-10-11 19:33 ` Jens Axboe [this message]
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
[not found] <tencent_2C6C333F9ED41B104B521B6E25D8BA6BBB08@qq.com>
2023-12-02 1:47 ` syzbot
[not found] <tencent_E68094D8E9BAEFDACCF878BA6C342CE16E0A@qq.com>
2023-12-02 2:33 ` syzbot
[not found] <tencent_3436E64AC8741F77C766E83DE336CA963209@qq.com>
2023-12-02 3:36 ` syzbot
[not found] <tencent_75CC257BBAC7BBA6337C9E541B054BF91B08@qq.com>
2023-12-02 5:14 ` 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=4661f4ef-44a0-402b-864b-83ef8d31f07e@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com \
--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