[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250519135632.GA38098@mit.edu>
Date: Mon, 19 May 2025 09:56:32 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Ethan Carter Edwards <ethan@...ancedwards.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
oe-kbuild-all@...ts.linux.dev, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] ext4: replace strcpy() with '.' assignment
On Mon, May 19, 2025 at 01:58:02PM +0800, kernel test robot wrote:
> Hi Ethan,
>
> kernel test robot noticed the following build errors:
Hi Ethan,
I would really appreciate it if you would at least do a build test
before sending out a patch. In addition, it would also be helpful if
you ran a smoke test, using "kvm-xfstests smoke". The instructions
for how to use kvm-xfstests can be found here[1], and it was designed
to be as easy as possible for people who are sending "drive-by
patches".
[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-quickstart.md
Running the smoketest only takes about 20 minutes; although if you
want to run more sophistcated testing there is also "kvm-xfstests -c
ext4/4k -g quick", or "kvm-xfstests -c ext4/4k -g auto", or if you
have a 24 hours to kill, there's always "kvm-xfststs full". (Although
these days I generally use gce-xfstests[2] since this can shard the test
runs across multiple VM's, so it only takes 2.5 hours of wall clock
time.)
[2] https://thunk.org/gce-xfstests
Cheers,
- TEd
Powered by blists - more mailing lists