From: Al Viro <viro@zeniv.linux.org.uk>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: amd-gfx@lists.freedesktop.org, "Deucher,
Alexander" <Alexander.Deucher@amd.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2][RFC] amdkfd CRIU fixes
Date: Tue, 4 Jun 2024 20:20:23 +0100 [thread overview]
Message-ID: <20240604192023.GT1629371@ZenIV> (raw)
In-Reply-To: <1cd7980e-1cfa-4470-b712-48d9d2658435@amd.com>
On Tue, Jun 04, 2024 at 02:16:00PM -0400, Felix Kuehling wrote:
>
> On 2024-06-03 22:14, Al Viro wrote:
> > Instead of trying to use close_fd() on failure exits, just have
> > criu_get_prime_handle() store the file reference without inserting
> > it into descriptor table.
> >
> > Then, once the callers are past the last failure exit, they can go
> > and either insert all those file references into the corresponding
> > slots of descriptor table, or drop all those file references and
> > free the unused descriptors.
> >
> > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>
> Thank you for the patches and the explanation. One minor nit-pick inline.
> With that fixed, this patch is
>
> Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
>
> I can apply this patch to amd-staging-drm-next, if you want. See one comment
> inline ...
Fine by me; I think this stuff would be better off in the relevant trees -
it's not as if we realistically could unexport close_fd() this cycle anyway,
more's the pity... So nothing I've got in my queue has that as a prereq and
it would definitely have better odds of getting tested in your tree.
prev parent reply other threads:[~2024-06-04 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604021255.GO1629371@ZenIV>
2024-06-04 2:13 ` [PATCH 1/2][RFC] amdgpu: fix a race in kfd_mem_export_dmabuf() Al Viro
2024-06-04 18:08 ` Felix Kuehling
2024-06-04 19:10 ` Al Viro
2024-06-04 19:17 ` [PATCH v2 " Al Viro
2024-06-05 9:14 ` [PATCH " Christian König
2024-06-06 21:57 ` Felix Kuehling
2024-06-04 2:14 ` [PATCH 2/2][RFC] amdkfd CRIU fixes Al Viro
2024-06-04 18:16 ` Felix Kuehling
2024-06-04 19:20 ` Al Viro [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=20240604192023.GT1629371@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).