From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+edfd15cd4246a3fc615a@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: invalid-free in io_clean_op
Date: Mon, 26 Sep 2022 11:04:03 +0100 [thread overview]
Message-ID: <cba736c2-2e5b-e433-2334-4e96624a8d5f@gmail.com> (raw)
In-Reply-To: <8c9845cf-a5fe-21c0-10a5-2369758dd23c@gmail.com>
On 9/25/22 18:54, Pavel Begunkov wrote:
> On 9/25/22 18:29, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: aaa11ce2ffc8 Add linux-next specific files for 20220923
>> git tree: linux-next
>> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1608cadf080000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=186d1ff305f10294
>> dashboard link: https://syzkaller.appspot.com/bug?extid=edfd15cd4246a3fc615a
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144acdef080000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10686540880000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+edfd15cd4246a3fc615a@syzkaller.appspotmail.com
>
> #syz test: git://git.kernel.dk/linux.git for-6.1/io_uring
Should be similar to the previous net/op_clean problem but
now zc and because of that we set CLEANUP too early. Just
a guess, will take a look at the repro
--
Pavel Begunkov
prev parent reply other threads:[~2022-09-26 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 17:29 [syzbot] KASAN: invalid-free in io_clean_op syzbot
2022-09-25 17:54 ` Pavel Begunkov
2022-09-25 18:15 ` syzbot
2022-09-26 13:49 ` Pavel Begunkov
2022-09-26 14:40 ` syzbot
2022-09-26 10:04 ` Pavel Begunkov [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=cba736c2-2e5b-e433-2334-4e96624a8d5f@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+edfd15cd4246a3fc615a@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 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.