From: syzbot <syzbot+cf285a028ffba71b2ef5@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] WARNING: refcount bug in io_send_zc_cleanup (2)
Date: Sat, 22 Mar 2025 07:21:04 -0700 [thread overview]
Message-ID: <67dec750.050a0220.31a16b.003e.GAE@google.com> (raw)
In-Reply-To: <67de616f.050a0220.31a16b.002b.GAE@google.com>
syzbot has bisected this issue to:
commit cc34d8330e036b6bffa88db9ea537bae6b03948f
Author: Jens Axboe <axboe@kernel.dk>
Date: Thu Mar 20 18:25:12 2025 +0000
io_uring/net: don't clear REQ_F_NEED_CLEANUP unconditionally
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15ef043f980000
start commit: d07de43e3f05 Merge tag 'io_uring-6.14-20250321' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17ef043f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13ef043f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=620facf12ff15d10
dashboard link: https://syzkaller.appspot.com/bug?extid=cf285a028ffba71b2ef5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16be1c4c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12223004580000
Reported-by: syzbot+cf285a028ffba71b2ef5@syzkaller.appspotmail.com
Fixes: cc34d8330e03 ("io_uring/net: don't clear REQ_F_NEED_CLEANUP unconditionally")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-22 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 7:06 [syzbot] [io-uring?] WARNING: refcount bug in io_send_zc_cleanup (2) syzbot
2025-03-22 9:04 ` Pavel Begunkov
2025-03-22 9:28 ` syzbot
2025-03-22 14:21 ` 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=67dec750.050a0220.31a16b.003e.GAE@google.com \
--to=syzbot+cf285a028ffba71b2ef5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox