[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240703182636.a04510e21e53b5afe82e60d9@linux-foundation.org>
Date: Wed, 3 Jul 2024 18:26:36 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: SeongJae Park <sj@...nel.org>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, "Liam R . Howlett"
<Liam.Howlett@...cle.com>, Vlastimil Babka <vbabka@...e.cz>, Matthew Wilcox
<willy@...radead.org>, Alexander Viro <viro@...iv.linux.org.uk>, Christian
Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>, Eric Biederman
<ebiederm@...ssion.com>, Kees Cook <kees@...nel.org>, Suren Baghdasaryan
<surenb@...gle.com>, Shuah Khan <shuah@...nel.org>, Brendan Higgins
<brendanhiggins@...gle.com>, David Gow <davidgow@...gle.com>, Rae Moar
<rmoar@...gle.com>
Subject: Re: [PATCH 0/7] Make core VMA operations internal and testable
On Thu, 4 Jul 2024 00:24:15 +0100 Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
> The self tests differ from this and other tests using the userland-stubbed
> kernel approach in that they test system call invocation and assert
> expectations.
>
> My point to Andrew was that we could potentially automatically run these
> tests as part of a self-test run as they are so quick, at least in the
> future, if that made sense.
Yes, I was thinking we'd just add a selftest which does (simplified,
of course)
cd ../../vma
make
./whatever
simply to cause this new code to be invoked when someone runs the
selftest suite.
Powered by blists - more mailing lists