xfs
[Top] [All Lists]

Re: [PATCH] kill INDUCE_IO_ERROR

To: Donald Douwsma <donaldd@xxxxxxx>
Subject: Re: [PATCH] kill INDUCE_IO_ERROR
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 18 Jun 2008 14:05:36 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <485892D7.4080000@sgi.com>
References: <20080523062323.GA32637@lst.de> <20080616101412.GA17939@lst.de> <485892D7.4080000@sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Wed, Jun 18, 2008 at 02:45:11PM +1000, Donald Douwsma wrote:
> Christoph Hellwig wrote:
> >On Fri, May 23, 2008 at 08:23:23AM +0200, Christoph Hellwig wrote:
> >>All the error injection is already enabled through ifdef DEBUG, so kill
> >>the never set second cpp symbol to activate it without the rest of the
> >>debugging infrastructure.
> >
> >Can I get a review on this absolutely trivial patch?
> 
> I'd like to keep INDUCE_IO_ERROR around so we have a way to introduce
> ioerrors in release builds during testing.
> 
> We could add it to xfs.h with the commented out QUOTADEBUG so people
> know we still want to use it.

cpp symbols not exposed by Kconfig will never get tested.  If you thing
it's really useful for release builds (which don't quite agree with) we
should just enable it unconditionally.  It's just in a few places, and
any branch predictor worth it's name should take care of the additional
branches without visible cost.


<Prev in Thread] Current Thread [Next in Thread>