mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: David Matlack <dmatlack@google.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	 Pratyush Yadav <pratyush@kernel.org>,
	 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>,
	 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: Fri, 06 Nov 2026 15:19:47 +0100	[thread overview]
Message-ID: <2vxzjymqhwjg.fsf@kernel.org> (raw)
In-Reply-To: <auu02-iDbVaEL-4v@google.com> (David Matlack's message of "Wed, 4 Nov 2026 22:42:35 +0000")

On Wed, Nov 04 2026, David Matlack wrote:

> On 2026-11-04 02:37 PM, Pasha Tatashin wrote:
>> On 11-04 17:59, Pratyush Yadav wrote:
>> > On Tue, Nov 03 2026, David Matlack wrote:
>> > [...]
>> > 
>> > 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.
>
> Agreed that it needs to be easier to review, but I'd like to keep the
> coverage. Here's what I have in mind for v4:
>
>  - Move the preserve-side checks that don't need a kexec into
>    liveupdate.c, like Pasha suggested in his earlier reply: which files
>    can be preserved (permissions, read-only and append-only files), the
>    frozen size while preserved, and unpreserve. Those then run with the
>    regular kselftests instead of only in vmtest.sh.
>
>  - Split the rest of luo_tmpfs into several smaller commits that add the
>    tested features incrementally, e.g. one for the test infrastructure
>    and basic retrieve, one for the open() flags and creation checks, and
>    one for block accounting. That makes the series longer, but each
>    commit is a few hundred lines and can be reviewed on its own.
>
> It will still be long, but I think having the test coverage is worth it.

Agreed.

>
> Does that sound reasonable?

Sounds good. But I think practically speaking, it is not possible to
review the tests as carefully as the main changes. I think I'll rely
more on my LLM for those.

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-11-06 14:19 UTC|newest]

Thread overview: 40+ 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 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 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-06 14:14       ` Pratyush Yadav
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-06 14:20       ` Pratyush Yadav
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-04 23:38     ` 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-06 14:11         ` Pratyush Yadav
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
2026-11-04 22:42       ` David Matlack
2026-11-06 14:19         ` Pratyush Yadav [this message]
2026-11-05 15:42 ` [PATCH v3 00/10] liveupdate: Preserve tmpfs files across Live Update Christian Brauner
2026-11-05 16:52   ` 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=2vxzjymqhwjg.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --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=pasha.tatashin@soleen.com \
    --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

all inboxes | Powered by JetHome®