public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] xfs: detect self referencing btree sibling pointers
Date: Wed, 4 May 2022 09:13:42 +1000	[thread overview]
Message-ID: <20220503231342.GD1098723@dread.disaster.area> (raw)
In-Reply-To: <20220503225314.GF8265@magnolia>

On Tue, May 03, 2022 at 03:53:14PM -0700, Darrick J. Wong wrote:
> On Mon, May 02, 2022 at 06:20:15PM +1000, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> > 
> > To catch the obvious graph cycle problem and hence potential endless
> > looping.
> > 
> > Signed-off-by: Dave Chinner <dchinner@redhat.com>
> > ---
> >  fs/xfs/libxfs/xfs_btree.c | 137 ++++++++++++++++++++++++++++----------
> >  1 file changed, 102 insertions(+), 35 deletions(-)
> > 
> > diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
> > index a8c79e760d8a..991fae6f500a 100644
> > --- a/fs/xfs/libxfs/xfs_btree.c
> > +++ b/fs/xfs/libxfs/xfs_btree.c
> > @@ -51,6 +51,50 @@ xfs_btree_magic(
> >  	return magic;
> >  }
> >  
> > +static xfs_failaddr_t
> 
> Minor nit: static inline?

Not necessary - the compiler will do that automatically if
optimisations are turned on (as they always are).  Modern compilers
are pretty aggressive at inlining code when they know there are no
other external references to the function.

> Reviewed-by: Darrick J. Wong <djwong@kernel.org>

Thanks!

-Dave.

-- 
Dave Chinner
david@fromorbit.com

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

Thread overview: 24+ 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 [this message]
2022-05-06  9:22   ` [xfs] 32678f1513: aim7.jobs-per-min -5.6% regression kernel test robot
2022-05-06 21:29     ` Dave Chinner
2022-05-07 11:09       ` [LKP] " Carel Si
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

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=20220503231342.GD1098723@dread.disaster.area \
    --to=david@fromorbit.com \
    --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