linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: gut error handling in xfs_trans_unreserve_and_mod_sb()
Date: Wed, 20 May 2020 17:03:34 +1000	[thread overview]
Message-ID: <20200520070334.GU2040@dread.disaster.area> (raw)
In-Reply-To: <20200520065334.GA25811@infradead.org>

On Tue, May 19, 2020 at 11:53:34PM -0700, Christoph Hellwig wrote:
> On Wed, May 20, 2020 at 07:48:39AM +1000, Dave Chinner wrote:
> > +	/*
> > +	 * Debug checks outside of the spinlock so they don't lock up the
> > +	 * machine if they fail.
> > +	 */
> > +	ASSERT(&mp->m_sb.sb_frextents >= 0);
> > +	ASSERT(&mp->m_sb.sb_dblocks >= 0);
> > +	ASSERT(&mp->m_sb.sb_agcount >= 0);
> 
> To stick to the theme of broken error handling I don't think this
> does what you think as this takes the address of each field, which
> will aways be >= 0.  I like the idea of the patch, though.

Ah, search and replace fail. I'll fix it.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2020-05-20  7:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 21:48 [PATCH 0/2] xfs: fix unecessary percpu counter overhead Dave Chinner
2020-05-19 21:48 ` [PATCH 1/2] xfs: gut error handling in xfs_trans_unreserve_and_mod_sb() Dave Chinner
2020-05-20  6:53   ` Christoph Hellwig
2020-05-20  7:03     ` Dave Chinner [this message]
2020-05-20  7:33   ` [PATCH 1/2 V2] " Dave Chinner
2020-05-20  7:48     ` Christoph Hellwig
2020-05-20 20:27       ` Darrick J. Wong
2020-05-20 21:55         ` Dave Chinner
2020-05-20 22:28           ` Darrick J. Wong
2020-05-20 22:37             ` Dave Chinner
2020-05-19 21:48 ` [PATCH 2/2] xfs: reduce free inode accounting overhead Dave Chinner
2020-05-20  6:56   ` Christoph Hellwig
2020-05-20 20:43   ` 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=20200520070334.GU2040@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).