[PATCH 0/5] tmpfs fixes

[Daniel Gomez <da.gomez@samsung.com>]

This series addresses some minor issues found in tmpfs FSQA suit test case.

The last patch adds information about mkfs and mount options for TEST and
SCRATCH devices. This is important to clarify especially if RECREATE_TEST_DEV
is disabled (which is the default case). The new output will look like the
following:

SECTION       -- tmpfs_noswap_huge_always
RECREATING    -- tmpfs on /media/test
FSTYP         -- tmpfs
PLATFORM      -- Linux/aarch64 localhost 6.10.0-rc3-dgc #6 SMP Thu Jun 13 22:48:46 CEST 2024
TEST device:
MKFS_OPTIONS  -- /media/test
MOUNT_OPTIONS -- -o size=1G /media/test /media/test
SCRATCH device:
MKFS_OPTIONS  -- /media/scratch
MOUNT_OPTIONS -- -o size=1G -o noswap,huge=always /media/scratch /media/scratch

Regarding $TMPFS_MOUNT_OPTIONS, when it is defined in the [default] section of
a configuration file, the mount options specified there will be prefixed to the
test section options. Is this the correct and expected behaviour?

Example:

```localhost.config
[default]
FSTYP=tmpfs
TEST_DIR=/media/test
SCRATCH_MNT=/media/scratch
SCRATCH_DEV=/media/scratch
RESULT_BASE=$PWD/results/$HOST/$(uname -r)
TEST_DEV=/media/test
CANON_DEVS=yes
TMPFS_MOUNT_OPTIONS="-o size=3G"

[tmpfs_noswap_huge_always]
TMPFS_MOUNT_OPTIONS="-o noswap,huge=always"
```

Note: The above config would result in '-o size=1G -o size=3G -o
noswap,huge=always' at mount time for tmpfs_noswap_huge_always section. The '-o
size=1G' is a hardcoded prefix mount option.

Daniel

Daniel Gomez (4):
  common/config: fix RECREATE_TEST_DEV initialization
  common/rc: add recreation support for tmpfs
  common/rc: fix scratch mount options for tmpfs
  common/rc: print scratch and test mount options

Hugh Dickins (1):
  generic/449: not run on tmpfs earlier

 check             |  4 ++++
 common/config     |  2 +-
 common/rc         | 25 ++++++++++++++++++++++---
 tests/generic/449 |  6 ++++++
 4 files changed, 33 insertions(+), 4 deletions(-)

-- 
2.43.0