From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: David Matlack <dmatlack@google.com>,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Christian Brauner <brauner@kernel.org>,
David Hildenbrand <david@kernel.org>,
Hugh Dickins <hughd@google.com>,
Jonathan Corbet <corbet@lwn.net>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Randy Dunlap <rdunlap@infradead.org>,
Samiullah Khawaja <skhawaja@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: [PATCH v3 10/10] selftests/liveupdate: Add a test for preserving tmpfs files
Date: Wed, 4 Nov 2026 14:37:59 -0500 [thread overview]
Message-ID: <auuJM8c-bE43NP54@google.com> (raw)
In-Reply-To: <2vxz1p90jzx4.fsf@kernel.org>
On 11-04 17:59, Pratyush Yadav wrote:
> On Tue, Nov 03 2026, David Matlack wrote:
>
> > Add luo_tmpfs, a kexec test for preserving tmpfs files and memfds, and
> > for retrieving tmpfs files onto a tmpfs mount with struct
> > liveupdate_shmem_retrieve_arg.
> >
> > Stage 1 preserves the source files of each test case. Stage 2 runs
> > each test case in its own directory, with its own tmpfs mounts, so that
> > block usage can be checked exactly with statfs() and st_blocks. The test
> > cases cover:
> >
> > - The restored file: contents, size, position, seals and holes, for
> > linked and unlinked source files.
> >
> > - Creating the file: it is created like with open(O_TMPFILE), with the
> > requested mode minus the umask, owned by the caller, and not linked
> > until userspace links it, unless it asked for O_EXCL. Also O_RDONLY
> > and O_WRONLY files, other open() flags such as O_APPEND, O_NONBLOCK
> > and O_CLOEXEC, read-only mounts, and directories that the caller
> > can't write to.
> >
> > - Preserving files that can't be written to: a binary while it is
> > executed, through a read-only fd, files on read-only mounts and
> > superblocks, and immutable files, including sparse ones, whose holes
> > are filled. Preserving someone else's file that the caller can't
> > write to fails, and so does preserving a file through a write-only
> > fd or an append-only file.
> >
> > - Executing restored binaries: a restored binary can be executed
> > before the session is finished if it was retrieved with O_RDONLY, but
> > not if it was retrieved for writing, since LUO keeps the file open
> > until then. These test cases execute copies of the test binary.
> >
> > - Block accounting: the file fits a mount of exactly its size, and a
> > large folio that extends past the end of the file is charged in full.
> > Running out of space, or hitting the memcg limit, fails permanently,
> > and leaves nothing charged to the mount or the memcg. The session can
> > still be finished.
> >
> > - memfds: they are only retrieved as memfds, with their seals, and
> > files from tmpfs mounts only onto a tmpfs mount.
> >
> > - Interactions with LUO: invalid arguments, which can be retried,
> > retrieving a token twice, and outgoing sessions.
> >
> > Also check that the size of a preserved file is frozen, and that the
> > test doesn't trigger kernel warnings.
> >
> > Enable CONFIG_TRANSPARENT_HUGEPAGE for the large folio test cases,
> > CONFIG_MEMCG for the memcg test case and CONFIG_TMPFS_XATTR for
> > FS_IOC_SETFLAGS. Those test cases are skipped without them.
> >
> > tmpfs quotas are not tested, since the test runs as root, which is not
> > subject to quota limits.
> >
> > Signed-off-by: David Matlack <dmatlack@google.com>
> > ---
> > tools/testing/selftests/liveupdate/Makefile | 1 +
> > tools/testing/selftests/liveupdate/config | 4 +
> > .../testing/selftests/liveupdate/luo_tmpfs.c | 2055 +++++++++++++++++
>
> Umm, no way I am reading all this...
>
> LLMs are great at generating tests, and I'm not saying there is no value
> in this. It is just that this massive code dump is unreviewable by
> humans. It is also unfair to the human reviewer because it took many
> orders of magnitude less effort to _write_ them with an LLM.
>
> What do you all reckon we should do about this? Trust the LLM to get the
> testing right? Do we give up human maintenance of tests entirely? Do we
> do fault injection to test the tests themselves?
>
> Or do we make the tests smaller and more human reviewable?
We need good test coverage, but I believe we can break this patch down
into smaller changes where tested features are incrementally added.
>
> > .../selftests/liveupdate/run-vmtests.sh | 1 +
> > 4 files changed, 2061 insertions(+)
> > create mode 100644 tools/testing/selftests/liveupdate/luo_tmpfs.c
> >
> [...]
>
> --
> Regards,
> Pratyush Yadav
--
Pasha
next prev parent reply other threads:[~2026-11-04 19:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 1:02 [PATCH v3 00/10] liveupdate: Preserve tmpfs files across Live Update David Matlack
2026-11-03 1:02 ` [PATCH v3 01/10] liveupdate: Pass user argument to file preserve and retrieve David Matlack
2026-11-04 1:03 ` sashiko-bot
2026-11-04 13:17 ` Pratyush Yadav
2026-11-03 1:02 ` [PATCH v3 02/10] selftests: liveupdate: Add tests for preserve and retrieve user argument David Matlack
2026-11-04 1:03 ` sashiko-bot
2026-11-04 13:26 ` Pratyush Yadav
2026-11-03 1:02 ` [PATCH v3 03/10] liveupdate: Allow file handlers to mark retrieve failures as retryable David Matlack
2026-11-04 14:12 ` Pratyush Yadav
2026-11-04 16:15 ` Pasha Tatashin
2026-11-03 1:02 ` [PATCH v3 04/10] mm: Rename memfd_luo to shmem_luo David Matlack
2026-11-04 14:25 ` Pratyush Yadav
2026-11-03 1:02 ` [PATCH v3 05/10] liveupdate: Don't WARN if tracking a retrieved file fails David Matlack
2026-11-04 14:32 ` Pratyush Yadav
2026-11-03 1:02 ` [PATCH v3 06/10] mm/shmem_luo: Don't make early retrieve failures permanent David Matlack
2026-11-04 15:01 ` Pratyush Yadav
2026-11-04 22:28 ` David Matlack
2026-11-03 1:02 ` [PATCH v3 07/10] mm/shmem_luo: Retrieve tmpfs files onto a tmpfs mount chosen by userspace David Matlack
2026-11-04 0:43 ` Pasha Tatashin
2026-11-04 16:27 ` Pratyush Yadav
2026-11-04 22:30 ` David Matlack
2026-11-03 1:02 ` [PATCH v3 08/10] mm/shmem_luo: Allow preserving tmpfs files that are still linked David Matlack
2026-11-04 0:43 ` Pasha Tatashin
2026-11-04 16:45 ` Pratyush Yadav
2026-11-04 22:32 ` David Matlack
2026-11-03 1:02 ` [PATCH v3 09/10] mm/shmem_luo: Allow retrieving tmpfs files with O_RDONLY David Matlack
2026-11-04 0:43 ` Pasha Tatashin
2026-11-04 16:52 ` Pratyush Yadav
2026-11-04 19:45 ` Pasha Tatashin
2026-11-04 22:35 ` David Matlack
2026-11-03 1:02 ` [PATCH v3 10/10] selftests/liveupdate: Add a test for preserving tmpfs files David Matlack
2026-11-04 0:43 ` Pasha Tatashin
2026-11-04 16:59 ` Pratyush Yadav
2026-11-04 19:37 ` Pasha Tatashin [this message]
2026-11-04 22:42 ` 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=auuJM8c-bE43NP54@google.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=hughd@google.com \
--cc=kexec@lists.infradead.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@google.com \
--cc=surenb@google.com \
--cc=vbabka@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