From: "Darrick J. Wong" <djwong@kernel.org>
To: da.gomez@samsung.com
Cc: fstests@vger.kernel.org, Zorro Lang <zlang@redhat.com>,
mcgrof@kernel.org, gost.dev@samsung.com,
Samsung Samsung <Daniel Gomez d+samsung@kruces.com>
Subject: Re: [PATCH v2 2/5] common/rc: add recreation support for tmpfs
Date: Mon, 1 Jul 2024 15:36:28 -0700 [thread overview]
Message-ID: <20240701223628.GJ103020@frogsfrogsfrogs> (raw)
In-Reply-To: <20240630-common-fixes-v2-2-16d26fb1dee0@samsung.com>
On Sun, Jun 30, 2024 at 11:52:41PM +0200, Daniel Gomez via B4 Relay wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
>
> Add support for test device recreation (RECREATE_TEST_DEV=true) for
> tmpfs.
>
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> ---
> common/rc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 163041fea..51827119c 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -604,6 +604,9 @@ _test_mkfs()
> pvfs2)
> # do nothing for pvfs2
> ;;
> + tmpfs)
Indentation problem here.
> + # do nothing for tmpfs
If we're recreating the test filesystem, shouldn't that unmount and
remount for tmpfs? Or at least rm -rf everything underneath it? That's
generally the effect of _test_mkfs for disk filesystems.
(That said, I'm much less familiar with non-disk filesystems...)
--D
> + ;;
> udf)
> $MKFS_UDF_PROG $MKFS_OPTIONS $* $TEST_DEV > /dev/null
> ;;
>
> --
> 2.43.0
>
>
>
next prev parent reply other threads:[~2024-07-01 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 21:52 [PATCH v2 0/5] common fixes Daniel Gomez via B4 Relay
2024-06-30 21:52 ` [PATCH v2 1/5] common/config: fix RECREATE_TEST_DEV initialization Daniel Gomez via B4 Relay
2024-06-30 21:52 ` [PATCH v2 2/5] common/rc: add recreation support for tmpfs Daniel Gomez via B4 Relay
2024-07-01 22:36 ` Darrick J. Wong [this message]
2024-07-05 21:46 ` Daniel Gomez (Samsung)
2024-07-08 17:34 ` Darrick J. Wong
2024-06-30 21:52 ` [PATCH v2 3/5] common/config: enable section parsing when recreation Daniel Gomez via B4 Relay
2024-06-30 21:52 ` [PATCH v2 4/5] common/rc: read config section mount options for scratch devs Daniel Gomez via B4 Relay
2024-07-12 9:26 ` Zirong Lang
2024-07-12 9:49 ` Zorro Lang
2024-07-15 8:17 ` Daniel Gomez
2024-08-05 12:04 ` Daniel Gomez
2024-08-06 13:11 ` Zorro Lang
2024-06-30 21:52 ` [PATCH v2 5/5] common/rc: print test mount options Daniel Gomez via B4 Relay
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=20240701223628.GJ103020@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=da.gomez@samsung.com \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=mcgrof@kernel.org \
--cc=zlang@redhat.com \
/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