public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Andrey Albershteyn <aalbersh@kernel.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/4] repair: add canonical names for the XR_INO_ constants
Date: Mon, 1 Dec 2025 07:23:00 +0100	[thread overview]
Message-ID: <20251201062300.GB19310@lst.de> (raw)
In-Reply-To: <z4sbdrflefzmzgshjhynq3mrvospl5mkipp4ogajqp44sntazc@cot4zzdmnqql>

On Fri, Nov 28, 2025 at 09:00:59AM +0100, Carlos Maiolino wrote:
> On Fri, Nov 28, 2025 at 07:37:00AM +0100, Christoph Hellwig wrote:
> > Add an array with the canonical name for each inode type so that code
> > doesn't have to implement switch statements for that, and remove the now
> > trivial process_misc_ino_types and process_misc_ino_types_blocks
> > functions.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > -
> 
> 
> >  static inline int
> >  dinode_fmt(
> >  	struct xfs_dinode *dino)
> > @@ -2261,16 +2180,20 @@ _("directory inode %" PRIu64 " has bad size %" PRId64 "\n"),
> >  	case XR_INO_BLKDEV:
> >  	case XR_INO_SOCK:
> >  	case XR_INO_FIFO:
> > -		if (process_misc_ino_types(mp, dino, lino, type))
> > -			return 1;
> > -		break;
> > -
> >  	case XR_INO_UQUOTA:
> >  	case XR_INO_GQUOTA:
> >  	case XR_INO_PQUOTA:
> > -		/* Quota inodes have same restrictions as above types */
> > -		if (process_misc_ino_types(mp, dino, lino, type))
> > +		/*
> > +		 * Misc inode types that have no associated data storage (fifos,
> > +		 * pipes, devices, etc.) mad thus must also have a zero size.
> 
> 		Perhaps is my non-native English, but this sentence
> 		doesn't make much sense to me. Not sure if 'mad' has
> 		some special meaning in this context?

that should be an "and"


  reply	other threads:[~2025-12-01  6:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  6:36 repair tidyups for metadir handling Christoph Hellwig
2025-11-28  6:36 ` [PATCH 1/4] repair: add a enum for the XR_INO_* values Christoph Hellwig
2025-11-28  7:53   ` Carlos Maiolino
2025-12-01  6:22     ` Christoph Hellwig
2025-12-01  9:00       ` Carlos Maiolino
2025-12-01 22:37         ` Darrick J. Wong
2025-11-28  6:37 ` [PATCH 2/4] repair: add canonical names for the XR_INO_ constants Christoph Hellwig
2025-11-28  8:00   ` Carlos Maiolino
2025-12-01  6:23     ` Christoph Hellwig [this message]
2025-12-01 22:47   ` Darrick J. Wong
2025-12-02  7:33     ` Christoph Hellwig
2025-12-02 17:59       ` Darrick J. Wong
2025-12-03  6:09         ` Christoph Hellwig
2025-12-04 17:18           ` Darrick J. Wong
2025-12-05  8:13             ` Christoph Hellwig
2025-12-05 16:29               ` Darrick J. Wong
2025-11-28  6:37 ` [PATCH 3/4] repair: factor out a process_dinode_metafile helper Christoph Hellwig
2025-11-28  8:05   ` Carlos Maiolino
2025-12-01 22:47   ` Darrick J. Wong
2025-11-28  6:37 ` [PATCH 4/4] repair: enhance process_dinode_metafile Christoph Hellwig
2025-11-28  8:15   ` Carlos Maiolino
2025-12-01  6:23     ` Christoph Hellwig
2025-12-01  9:01       ` Carlos Maiolino
2025-12-01 22:48   ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2025-12-08  7:11 repair tidyups for metadir handling v2 Christoph Hellwig
2025-12-08  7:11 ` [PATCH 2/4] repair: add canonical names for the XR_INO_ constants Christoph Hellwig
2025-12-08 17:36   ` Darrick J. Wong
2025-12-09  6:57     ` Christoph Hellwig
2025-12-09 15:59   ` Darrick J. Wong
2025-12-09 16:20     ` Christoph Hellwig
2025-12-09 16:26       ` Darrick J. Wong
2025-12-10  5:54 repair tidyups for metadir handling v3 Christoph Hellwig
2025-12-10  5:54 ` [PATCH 2/4] repair: add canonical names for the XR_INO_ constants 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=20251201062300.GB19310@lst.de \
    --to=hch@lst.de \
    --cc=aalbersh@kernel.org \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --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