From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
mm-commits@vger.kernel.org, skhawaja@google.com,
shuah@kernel.org, rppt@kernel.org, pratyush@kernel.org,
dmatlack@google.com, pasha.tatashin@soleen.com
Subject: Re: + liveupdate-prevent-double-management-of-files.patch added to mm-new branch
Date: Wed, 25 Mar 2026 17:21:11 -0700 [thread overview]
Message-ID: <20260326002112.77105-1-sj@kernel.org> (raw)
In-Reply-To: <20260324150331.BBF14C19424@smtp.kernel.org>
Hello Andrew,
On Tue, 24 Mar 2026 08:03:31 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> The patch titled
> Subject: liveupdate: prevent double management of files
> has been added to the -mm mm-new branch. Its filename is
> liveupdate-prevent-double-management-of-files.patch
[...]
> ------------------------------------------------------
> From: Pasha Tatashin <pasha.tatashin@soleen.com>
> Subject: liveupdate: prevent double management of files
> Date: Mon, 23 Mar 2026 20:31:44 +0000
>
> Patch series "liveupdate: prevent double preservation", v2.
>
> Currently, LUO does not prevent the same file from being preserved twice
> across different active sessions.
>
> Because LUO preserves files of absolutely different types: memfd, and
> upcoming vfiofd [1], iommufd [2], guestmefd (and possible kvmfd/cpufd).
> There is no common private data or guarantee on how to prevent that the
> same file is not preserved twice beside using inode or some slower and
> expensive method like hashtables.
>
>
>
> Currently, LUO does not prevent the same file from being managed twice
> across different active sessions.
Seems the usual "This patch (of X):" line above this paragraph is mistakenly
not added?
No issue for me, but I just wanted to inform you for a case that you care about
that.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-26 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:03 + liveupdate-prevent-double-management-of-files.patch added to mm-new branch Andrew Morton
2026-03-26 0:21 ` SeongJae Park [this message]
2026-03-26 0:34 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2026-03-27 1:19 Andrew Morton
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=20260326002112.77105-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhawaja@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.