All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs: validate v5 feature fields
Date: Tue, 3 May 2022 16:28:58 -0700	[thread overview]
Message-ID: <20220503232858.GM8265@magnolia> (raw)
In-Reply-To: <20220503231858.GE1098723@dread.disaster.area>

On Wed, May 04, 2022 at 09:18:58AM +1000, Dave Chinner wrote:
> On Tue, May 03, 2022 at 03:59:18PM -0700, Darrick J. Wong wrote:
> > On Mon, May 02, 2022 at 06:20:18PM +1000, Dave Chinner wrote:
> > > From: Dave Chinner <dchinner@redhat.com>
> > > 
> > > Because stupid dumb fuzzers.
> > 
> > Dumb question: Should we make db_flds[] in db/sb.c (userspace) report
> > each individual feature flag as a field_t?
> 
> Maybe, but we do already have the versionnum command that dumps the
> feature bits in text/human readable format....

The fuzz tests in fstests just do:

# xfs_db /dev/sda -c '<goto metadata>' -c 'print' | awk '{print $1}'

to find the fields that it should fuzz, so if we don't call out
individual bit fields in the features flags, it'll never fuzz them.
I guess I"ll look into changing that...

--D

> > I've been wondering why none
> > of my fuzz tests ever found these problems, and it's probably because
> > it never hit the magic bits that $scriptkiddie happened to hit.
> 
> Yeah, you've probably never cleared just the dirv2 bit. That one has
> an assert on it these days because the kernel only supports v2-based
> directory formats.  In other cases, things still work but we
> probably don't do the right thing for v5 formats :)
> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

      reply	other threads:[~2022-05-03 23:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  8:20 [PATCH 0/4] xfs: fix random format verification issues Dave Chinner
2022-05-02  8:20 ` [PATCH 1/4] xfs: detect self referencing btree sibling pointers Dave Chinner
2022-05-03 14:53   ` Christoph Hellwig
2022-05-03 21:27     ` Dave Chinner
2022-05-03 22:53   ` Darrick J. Wong
2022-05-03 23:13     ` Dave Chinner
2022-05-06  9:22   ` [xfs] 32678f1513: aim7.jobs-per-min -5.6% regression kernel test robot
2022-05-06  9:22     ` kernel test robot
2022-05-06 21:29     ` Dave Chinner
2022-05-06 21:29       ` Dave Chinner
2022-05-07 11:09       ` [LKP] " Carel Si
2022-05-07 11:09         ` Carel Si
2022-05-09  0:03         ` [LKP] " Dave Chinner
2022-05-09  0:03           ` Dave Chinner
2022-05-02  8:20 ` [PATCH 2/4] xfs: validate inode fork size against fork format Dave Chinner
2022-05-03 14:55   ` Christoph Hellwig
2022-05-03 22:55   ` Darrick J. Wong
2022-05-02  8:20 ` [PATCH 3/4] xfs: set XFS_FEAT_NLINK correctly Dave Chinner
2022-05-03 14:56   ` Christoph Hellwig
2022-05-03 22:55   ` Darrick J. Wong
2022-05-02  8:20 ` [PATCH 4/4] xfs: validate v5 feature fields Dave Chinner
2022-05-02  9:44   ` kernel test robot
2022-05-02 12:37   ` kernel test robot
2022-05-03 15:00   ` Christoph Hellwig
2022-05-03 21:26     ` Dave Chinner
2022-05-03 22:59   ` Darrick J. Wong
2022-05-03 23:18     ` Dave Chinner
2022-05-03 23:28       ` 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=20220503232858.GM8265@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.