From: Jens Axboe <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] WARNING in io_link_timeout_fn
Date: Wed, 12 May 2021 14:56:44 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/12/21 2:28 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 88b06399 Merge tag 'for-5.13-rc1-part2-tag' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13c0d265d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=807beec6b4d66bf1
> dashboard link: https://syzkaller.appspot.com/bug?extid=5a864149dd970b546223
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10436223d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1715208bd00000
>
> The issue was bisected to:
>
> commit 91f245d5d5de0802428a478802ec051f7de2f5d6
> Author: Jens Axboe <[email protected]>
> Date: Tue Feb 9 20:48:50 2021 +0000
>
> io_uring: enable kmemcg account for io_uring requests
Don't think that's right...
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144fbb23d00000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=164fbb23d00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=124fbb23d00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: [email protected]
> Fixes: 91f245d5d5de ("io_uring: enable kmemcg account for io_uring requests")
I think this one is already fixed:
#syz test: git://git.kernel.dk/linux-block.git io_uring-5.13
--
Jens Axboe
next prev parent reply other threads:[~2021-05-12 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:28 [syzbot] WARNING in io_link_timeout_fn syzbot
2021-05-12 20:56 ` Jens Axboe [this message]
2021-05-12 22:38 ` syzbot
2021-05-13 21:03 ` Pavel Begunkov
2021-05-14 0:08 ` syzbot
2021-05-14 0:39 ` Pavel Begunkov
2021-05-14 1:05 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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