Re: [PATCH v2 3/7] create_tmpfs: Enable mounting tmpfs file systems for testing

[Luis Chamberlain <mcgrof@kernel.org>]

On Thu, Jan 25, 2024 at 02:39:51PM +0000, Chuck Lever III wrote:
> 
> 
> > On Jan 25, 2024, at 9:26 AM, Luis Chamberlain <mcgrof@kernel.org> wrote:
> > 
> > On Wed, Jan 03, 2024 at 10:08:39AM -0500, Chuck Lever wrote:
> >> From: Chuck Lever <chuck.lever@oracle.com>
> >> 
> >> To enable tmpfs as a generic test target, add a playbook for
> >> mounting a tmpfs file system. The new playbook is similar to
> >> the create_partition playbook: it creates a persistent fstab
> >> entry, but does not need to reserve a block device for the
> >> new file system.
> >> 
> >> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> > 
> > It would seem this is to use tmpfs for some purpose. Note that fstests
> > in kdevops already does have proper full profiles support to help test
> > tmpfs with all the possible bells and whistles available as different
> > profiles. That is, each possibe variation as a different guest / node.
> > That is being used by Daniel Gomez to first create a public baseline
> > for tmpfs so that we can then add support for large folios for it.
> 
> The fstests workflow has support for tmpfs, true.
> 
> But we need to mount tmpfs shares in the NFS server, and the new
> gitr workflow needs to mount tmpfs for testing. That is the
> underlying need being addressed here.

Sure, I get it, now that I read the rest of the patches the goal seems
clear. The notes I made about having gitr support when one is already
enabling a dedicated fstests workflow in the other thread would allow us
to augment existing tmpfs fstests testing with this, so we can do both
in one kdevops setup for tmpfs:

make fstests-baseline
make gitr-baseline

  Luis