public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: jim owens <jowens@hp.com>
Cc: Chris Mason <chris.mason@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	Eric Sesterhenn <snakebyte@gmx.de>,
	linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: Warning and BUG with btrfs and corrupted image
Date: Wed, 25 Feb 2009 20:54:11 +0100	[thread overview]
Message-ID: <20090225195411.GI2645@elf.ucw.cz> (raw)
In-Reply-To: <498AF570.9030803@hp.com>

On Thu 2009-02-05 09:19:28, jim owens wrote:
> Pavel Machek wrote:
>>> If you don't want it, don't compile it in.  The Kconfig text is very
>>> clear.
>>
>> No, I'd not expect that option to panic systems. That's why I
>> suggested:
>>
>> diff --git a/fs/xfs/Kconfig b/fs/xfs/Kconfig
>> index 29228f5..b7ac847 100644
>> --- a/fs/xfs/Kconfig
>> +++ b/fs/xfs/Kconfig
>> @@ -77,4 +77,7 @@ config XFS_DEBUG
>>  	  Note that the resulting code will be HUGE and SLOW, and probably
>>  	  not useful unless you are debugging a particular problem.
>>  +	  Turning this option on will result in kernel panicking any time
>> +	  it detects on-disk corruption.
>> +
>>  	  Say N unless you are an XFS developer, or you play one on TV.
>
> If you really want a better warning it should simply be:
>
>           Choosing Y will make XFS panic on survivable events.

Can we get that line there?

> I understand you may have a concern that "normal users" will select
> the debug option by mistake, but I don't think that is realistic.
> My experience is they will not build custom debug kernels even if
> you beg them to.  They will only use the distro build and a
> distro should never turn this option on outside their own labs.
>
> Any non-xfs kernel developer who turns this on and gets
> snake bit will only do it once.

One bite per developer is one bite too many..
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-02-25 19:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 14:21 Warning and BUG with btrfs and corrupted image Eric Sesterhenn
2009-01-13 14:40 ` Chris Mason
2009-01-13 14:43   ` Eric Sesterhenn
2009-01-15  2:13     ` Chris Mason
2009-01-18 17:40     ` Pavel Machek
2009-01-20  6:31       ` Eric Sesterhenn
2009-01-20  9:34         ` Pavel Machek
2009-01-20 10:11         ` Dave Chinner
2009-01-20 10:15           ` Eric Sesterhenn
2009-01-20 12:59             ` Dave Chinner
2009-01-20 13:28               ` Christoph Hellwig
2009-01-20 22:20                 ` Pavel Machek
2009-01-21  4:00                   ` Dave Chinner
2009-01-26 16:27                     ` Pavel Machek
2009-01-26 20:06                       ` [Discussion] Apparent inconsistancies in use of io_align, io_width & sector_size ashford
2009-02-01  1:40                       ` Warning and BUG with btrfs and corrupted image Dave Chinner
2009-02-04 18:29                         ` Pavel Machek
2009-02-05  8:59                           ` Dave Chinner
2009-02-05  9:02                             ` Pavel Machek
2009-02-05 13:02                               ` Chris Mason
2009-02-05 13:50                                 ` Pavel Machek
2009-02-05 14:19                                   ` jim owens
2009-02-25 19:54                                     ` Pavel Machek [this message]
2009-01-20 17:34               ` Eric Sesterhenn
2009-01-20 22:18                 ` Pavel Machek
2009-01-21  9:36                   ` Eric Sesterhenn
2009-01-20 13:11         ` Chris Mason
2009-01-20 16:51           ` Eric Sesterhenn
2009-01-22  2:15             ` Phillip Lougher

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=20090225195411.GI2645@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=chris.mason@oracle.com \
    --cc=hch@infradead.org \
    --cc=jowens@hp.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snakebyte@gmx.de \
    /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