From: Pavel Begunkov <[email protected]>
To: Mark Harmstone <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH 1/2] io_uring/cmd: let cmds to know about dying task
Date: Sun, 3 Nov 2024 22:01:49 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 10/31/24 16:32, Mark Harmstone wrote:
> From: Pavel Begunkov <[email protected]>
>
> When the taks that submitted a request is dying, a task work for that
> request might get run by a kernel thread or even worse by a half
> dismantled task. We can't just cancel the task work without running the
> callback as the cmd might need to do some clean up, so pass a flag
> instead. If set, it's not safe to access any task resources and the
> callback is expected to cancel the cmd ASAP.
I was just going to write that you didn't CC io_uring for the
rest of the series, but I can't find it in the btrfs list, did
did something go wrong?
Regardless, I think it should be fine to merge it through
the btrfs tree
--
Pavel Begunkov
next prev parent reply other threads:[~2024-11-03 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 16:32 [PATCH 1/2] io_uring/cmd: let cmds to know about dying task Mark Harmstone
2024-11-01 3:14 ` Ming Lei
2024-11-03 22:01 ` Pavel Begunkov [this message]
2024-11-04 0:13 ` 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 \
[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