From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH] io_uring/net: fix sendzc double notif flush
Date: Sat, 22 Mar 2025 08:35:37 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <e1306007458b8891c88c4f20c966a17595f766b0.1742643795.git.asml.silence@gmail.com>
On Sat, 22 Mar 2025 11:47:27 +0000, Pavel Begunkov wrote:
> refcount_t: underflow; use-after-free.
> WARNING: CPU: 0 PID: 5823 at lib/refcount.c:28 refcount_warn_saturate+0x15a/0x1d0 lib/refcount.c:28
> RIP: 0010:refcount_warn_saturate+0x15a/0x1d0 lib/refcount.c:28
> Call Trace:
> <TASK>
> io_notif_flush io_uring/notif.h:40 [inline]
> io_send_zc_cleanup+0x121/0x170 io_uring/net.c:1222
> io_clean_op+0x58c/0x9a0 io_uring/io_uring.c:406
> io_free_batch_list io_uring/io_uring.c:1429 [inline]
> __io_submit_flush_completions+0xc16/0xd20 io_uring/io_uring.c:1470
> io_submit_flush_completions io_uring/io_uring.h:159 [inline]
>
> [...]
Applied, thanks!
[1/1] io_uring/net: fix sendzc double notif flush
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-22 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 11:47 [PATCH] io_uring/net: fix sendzc double notif flush Pavel Begunkov
2025-03-22 14:35 ` Jens Axboe [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=174265413772.771654.8140235260115879684.b4-ty@kernel.dk \
[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