From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs/507: use mount -t xfs
Date: Wed, 29 Jul 2026 17:49:30 +0200 [thread overview]
Message-ID: <20260729154930.GA18075@lst.de> (raw)
In-Reply-To: <20260729154650.GC7371@frogsfrogsfrogs>
On Wed, Jul 29, 2026 at 08:46:50AM -0700, Darrick J. Wong wrote:
> On Wed, Jul 29, 2026 at 02:59:55PM +0200, Christoph Hellwig wrote:
> > Sometimes mount wants to try every other file system but XFS when
> > mounting the loop image, making this test fail. Force mounting as XFS
> > to make it reliably pass.
>
> Weird. Do you know why it does that? Did the kernel really skip xfs or
> were the sb verifiers simply running in quiet mode?
Not really. I also happens in weird patches, I can reproduce it a few
times in a row, but just when I get ready to investigate the problem,
it goes away.
prev parent reply other threads:[~2026-07-29 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 12:59 [PATCH] xfs/507: use mount -t xfs Christoph Hellwig
2026-07-29 15:46 ` Darrick J. Wong
2026-07-29 15:49 ` Christoph Hellwig [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=20260729154930.GA18075@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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