From: syzbot <syzbot+1aa0bce76589e2e98756@syzkaller.appspotmail.com>
To: axboe@kernel.dk
Cc: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: ODEBUG bug in __io_put_task
Date: Thu, 12 Jan 2023 09:43:18 -0800 [thread overview]
Message-ID: <000000000000fa9db705f214a6c2@google.com> (raw)
In-Reply-To: <b130dd91-0871-6138-9a40-8499fb776875@kernel.dk>
> On 1/12/23 3:14 AM, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 0a093b2893c7 Add linux-next specific files for 20230112
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=14d269ce480000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=835f3591019836d5
>> dashboard link: https://syzkaller.appspot.com/bug?extid=1aa0bce76589e2e98756
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>>
>> Unfortunately, I don't have any reproducer for this issue yet.
>
> I know there's no reproducer yet, but when there is:
>
> #syz test: git://git.kernel.dk/linux.git for-next
This crash does not have a reproducer. I cannot test it.
>
> All of the ones from today was due to a buggy patch that was staged
> for 6.2, should all be gone with the updated branches.
>
> --
> Jens Axboe
>
>
prev parent reply other threads:[~2023-01-12 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:14 [syzbot] WARNING: ODEBUG bug in __io_put_task syzbot
2023-01-12 10:37 ` Pavel Begunkov
2023-01-12 10:39 ` syzbot
2023-01-12 17:43 ` Jens Axboe
2023-01-12 17:43 ` syzbot [this message]
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=000000000000fa9db705f214a6c2@google.com \
--to=syzbot+1aa0bce76589e2e98756@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--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.