Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Hans Holmberg <hans.holmberg@wdc.com>,
	linux-xfs@vger.kernel.org, aalbersh@kernel.org, cem@kernel.org
Subject: Re: [PATCH] libxfs: report device open errors during topology probing
Date: Wed, 2 Sep 2026 09:20:25 -0700	[thread overview]
Message-ID: <20260902162025.GU1933798@frogsfrogsfrogs> (raw)
In-Reply-To: <20260902055954.GA24431@lst.de>

On Wed, Sep 02, 2026 at 07:59:54AM +0200, Christoph Hellwig wrote:
> On Tue, Sep 01, 2026 at 10:46:27AM +0200, Hans Holmberg wrote:
> > > I wonder if there are any valid failures from blkid_new_probe_from_filename
> > > where we'd want to continue?  Probably not as it doesn't really have an
> > > obvious failure path, but so far we continue here.  So the print is useful
> > > for sure, but I wonder if failing here might cause regressions in some
> > > really odd use case (containers without sysfs?  Although we'd run into
> > > trouble with that quickly in other places).
> > 
> > 
> > Yeah, it might be safer to just print the warning, and that would solve
> > my problem (no instructive error message),
> > 
> > On the other hand it's nice to fail early - but not if it causes regressions
> > of course.
> 
> Yeah, failing early is nice, but I'm a bit fearful we might break
> existing (but really weird setups).

AFAICT hidden sysfs doesn't seem to break libbkid's probing of devices:

# mount moo /sys/ -t tmpfs ; mkfs.xfs -f /dev/sda
meta-data=/dev/sda               isize=512    agcount=4, agsize=644992 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=1
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=1
         =                       exchange=1   metadir=1
data     =                       bsize=4096   blocks=2579968, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1, parent=1
log      =internal log           bsize=4096   blocks=16384, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
         =                       rgcount=0    rgsize=268435456 extents
         =                       zoned=0      start=0 reserved=0
Discarding blocks...Done.

--D

  reply	other threads:[~2026-09-02 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 11:28 [PATCH] libxfs: report device open errors during topology probing Hans Holmberg
2026-08-31  7:10 ` Christoph Hellwig
2026-09-01  8:46   ` Hans Holmberg
2026-09-02  5:59     ` Christoph Hellwig
2026-09-02 16:20       ` Darrick J. Wong [this message]
2026-09-03  5:35         ` Christoph Hellwig

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=20260902162025.GU1933798@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=cem@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.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