From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: tarunsahu@google.com, linux-kselftest@vger.kernel.org,
rppt@kernel.org, shuah@kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, vipinsh@google.com,
linux-kernel@vger.kernel.org, dmatlack@google.com,
kexec@lists.infradead.org, pratyush@kernel.org,
graf@amazon.com
Subject: Re: [PATCH v1 3/7] liveupdate: Pass user argument to file preserve and retrieve
Date: Tue, 20 Oct 2026 12:20:28 +0200 [thread overview]
Message-ID: <2vxzfqy0hdw3.fsf@kernel.org> (raw)
In-Reply-To: <CA+CK2bD83qVv54_Wps4GRr9otg32pW2A01WVTo-gTR=oYs95Vw@mail.gmail.com> (Pasha Tatashin's message of "Mon, 19 Oct 2026 15:31:50 -0400")
On Mon, Oct 19 2026, Pasha Tatashin wrote:
> On Mon, Oct 19, 2026 at 3:26 PM <tarunsahu@google.com> wrote:
>>
>>
>> As Per Today's Hypervisor liveupdate meeting, This patch will be picked
>> by @dmatlack@google.com for latest tmpfs preservation series.
>>
>> I have a suggestion to make here.
>>
>> Let's send this patch as a saperate patch so that I can also use this in
>> my guest_memfd preservation work. This will help landing this feature
>> sooner and unblock other subsystem who needs it.
>>
>> Let me know what you think?
>
> Hi Tarun,
>
> You can include this patch the next time you send your guest_memfd
> patches. Whichever series lands first will pull in this change.
>
> We are trying not to merge new features without an actual user,
> especially ones as important as those changing the uapi. I think tmpfs
> preservation may actually make it easier to land, as it only changes
> the code that we maintain.
+1, let's use tmpfs preservation to land this change. It is a simple and
relatively small change compared to guest_memfd preservation.
[...]
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-10-20 10:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 9:38 [PATCH v1 0/7] liveupdate: tmpfs preservation and early freeze Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 1/7] liveupdate: Add LIVEUPDATE_SESSION_FREEZE ioctl to freeze sessions early Pasha Tatashin
2026-10-20 11:08 ` Pratyush Yadav
2026-10-20 14:30 ` Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 2/7] selftests: liveupdate: Add tests for LIVEUPDATE_SESSION_FREEZE Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 3/7] liveupdate: Pass user argument to file preserve and retrieve Pasha Tatashin
2026-10-19 19:26 ` tarunsahu
2026-10-19 19:31 ` Pasha Tatashin
2026-10-20 10:20 ` Pratyush Yadav [this message]
2026-10-15 9:38 ` [PATCH v1 4/7] selftests: liveupdate: Add tests for preserve and retrieve user argument Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 5/7] liveupdate: Allow file handlers to mark retrieve failures as retryable Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 6/7] mm/memfd_luo: Support tmpfs preservation and retrieval Pasha Tatashin
2026-10-15 9:38 ` [PATCH v1 7/7] selftests: liveupdate: Add test coverage for " Pasha Tatashin
2026-10-15 17:48 ` [PATCH v1 0/7] liveupdate: tmpfs preservation and early freeze David Matlack
2026-10-15 18:23 ` Pasha Tatashin
2026-10-15 18:54 ` David Matlack
2026-10-15 20:38 ` Pasha Tatashin
2026-10-15 21:53 ` David Matlack
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=2vxzfqy0hdw3.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=tarunsahu@google.com \
--cc=vipinsh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox