From: Fudam <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: Waiman Long <[email protected]>,
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: Bug: slab-use-after-free Read in try_to_wake_up
Date: Fri, 27 Dec 2024 04:45:14 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
> Kun Hu, can you try out the patch I sent? It should likely be
> it, but I couldn't reproduce without hand tailoring the kernel
> code with sleeping and such.
Okay, I’ll try again. Please wait for me for a moment. But you mean you couldn’t reproduce using the c program I provided unless you tailor the kernel code?
> 在 2024年12月27日,00:56,Pavel Begunkov <[email protected]> 写道:
>
> On 12/26/24 03:43, Kun Hu wrote:
>>> This is not caused by a locking bug. The freed structure is a task_struct which is passed by io_sq_thread() to try_to_wake_up(). So the culprit is probably in the io_uring code. cc'ing the io_uring developers for further review.
>> Thanks. This also seems to involve sqpoll.c and io_uring.c. I'm sending an email to both Pavel Begunkov and Jens Axboe, with a cc to io_uring.
>
> Kun Hu, can you try out the patch I sent? It should likely be
> it, but I couldn't reproduce without hand tailoring the kernel
> code with sleeping and such.
>
> --
> Pavel Begunkov
>
>
next prev parent reply other threads:[~2024-12-26 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2024-12-25 21:11 ` Bug: slab-use-after-free Read in try_to_wake_up Waiman Long
2024-12-26 3:43 ` Kun Hu
2024-12-26 16:57 ` Pavel Begunkov
2024-12-26 20:45 ` Fudam [this message]
2024-12-28 12:13 ` Pavel Begunkov
2024-12-26 12:24 ` Pavel Begunkov
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=DA2747F7-5D2A-4515-9764-B214AAD1DB37@m.fudan.edu.cn \
[email protected] \
[email protected] \
[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