FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: David Timber <dxdt@dev.snart.me>, Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] generic/740: set env for mkfs.exfat
Date: Thu, 25 Jun 2026 11:45:16 -0700	[thread overview]
Message-ID: <20260625184516.GQ6070@frogsfrogsfrogs> (raw)
In-Reply-To: <20260619045306.GA24829@lst.de>

On Fri, Jun 19, 2026 at 06:53:06AM +0200, Christoph Hellwig wrote:
> On Fri, Jun 19, 2026 at 04:22:35AM +0900, David Timber wrote:
> > Foreign filesystem detection is added in exfatprogs version 1.4.1. To
> > maintain backward compatibility, mkfs.exfat refuses to format the device
> > only when it's run from terminal with a tty associated to it.
> > 
> > This is similar to how e2fsprogs work around the issue. However,
> > with exfatprogs, this behaviour can be overridden with the special
> > environment variable EXFAT_TTY_OVERRIDE to simulate shell invocation by
> > user.
> > 
> > Signed-off-by: David Timber <dxdt@dev.snart.me>
> > ---
> >  tests/generic/740 | 15 ++++++++++++++-
> >  1 file changed, 14 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tests/generic/740 b/tests/generic/740
> > index ce55200f..4f8bf099 100755
> > --- a/tests/generic/740
> > +++ b/tests/generic/740
> > @@ -28,6 +28,18 @@ _require_block_device "${SCRATCH_DEV}"
> >  # not all the FS support zoned block device
> >  _require_non_zoned_device "${SCRATCH_DEV}"
> >  
> > +mkfs_preop=""
> > +mkfs_preargs=""
> > +mkfs_postargs=""
> > +
> > +case "$FSTYP" in
> > +exfat)
> > +	# For backward compatibility, mkfs.exfat refuses to format only when run
> > +	# from a tty. This env var should override the behaviour if supported.
> > +	mkfs_preop="EXFAT_TTY_OVERRIDE=1"
> > +	;;
> > +esac
> > +
> >  echo "Silence is golden."
> >  for fs in `echo ${MKFS_PROG}.* | sed -e "s:${MKFS_PROG}.::g"`
> >  do
> > @@ -83,7 +95,8 @@ do
> >  		# next, ensure we don't overwrite it
> >  
> >  		echo "=== Attempting $FSTYP overwrite of $fs..." >>$seqres.full
> > -		${MKFS_PROG} -t $FSTYP $SCRATCH_DEV >>$seqres.full 2>&1
> > +		eval $mkfs_preop ${MKFS_PROG} -t $FSTYP $mkfs_preargs $SCRATCH_DEV $mkfs_postargs \
> 
> breaking up the long line still would be nice here, i.e. keep at 80
> characters.  Else looks good.

I wonder why we don't just redirect stdin from /dev/null, it's not like
we want to capture user input anyway...

--D

      reply	other threads:[~2026-06-25 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 19:22 [PATCH 1/2] generic/740: set env for mkfs.exfat David Timber
2026-06-18 19:22 ` [PATCH 2/2] generic/740: add --force option to mkfs.ntfs David Timber
2026-06-19  4:53   ` Christoph Hellwig
2026-06-25 18:45   ` Darrick J. Wong
2026-06-19  4:53 ` [PATCH 1/2] generic/740: set env for mkfs.exfat Christoph Hellwig
2026-06-25 18:45   ` Darrick J. Wong [this message]

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=20260625184516.GQ6070@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=dxdt@dev.snart.me \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=zlang@kernel.org \
    /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