[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4661f4ef-44a0-402b-864b-83ef8d31f07e@kernel.dk>
Date: Fri, 11 Oct 2024 13:33:57 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+ed812ed461471ab17a0c@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4)
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@...nel.dk> wrote:
>>
>> On Thu, Nov 30, 2023 at 2:17?PM syzbot <syzbot+ed812ed461471ab17a0c@...kaller.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
Powered by blists - more mailing lists