public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Pavel Machek <pavel@suse.cz>
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: Thu, 05 Feb 2009 09:19:28 -0500	[thread overview]
Message-ID: <498AF570.9030803@hp.com> (raw)
In-Reply-To: <20090205135011.GA2294@elf.ucw.cz>

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.

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.

jim

  reply	other threads:[~2009-02-05 14:19 UTC|newest]

Thread overview: 42+ 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-02-01  1:40                       ` 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 [this message]
2009-02-25 19:54                                     ` Pavel Machek
2009-01-20 17:34               ` Eric Sesterhenn
2009-01-20 22:18                 ` Pavel Machek
2009-01-21  9:36                   ` Eric Sesterhenn
2009-01-21  3:57                 ` Corrupted XFS log replay oops. (was Re: Warning and BUG with btrfs and corrupted image) Dave Chinner
2009-01-21  4:03                   ` Nick Piggin
2009-01-22  4:37                     ` [PATCH] Re: Corrupted XFS log replay oops Dave Chinner
2009-01-22  5:50                       ` Felix Blyakher
2009-01-22  6:11                       ` Christoph Hellwig
2009-01-22  8:35                         ` Eric Sesterhenn
2009-01-22 10:06                         ` Eric Sesterhenn
2009-01-22 23:37                           ` Dave Chinner
2009-01-23  1:10                             ` Dave Chinner
2009-01-22 23:35                         ` Dave Chinner
2009-01-23  0:02                         ` Dave Chinner
2009-01-23  0:06                           ` Christoph Hellwig
2009-01-23  6:20                             ` Felix Blyakher
2009-01-21  4:03                   ` Corrupted XFS log replay oops. (was Re: Warning and BUG with btrfs and corrupted image) Dave Chinner
2009-01-20 13:11         ` Warning and BUG with btrfs and corrupted image 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=498AF570.9030803@hp.com \
    --to=jowens@hp.com \
    --cc=chris.mason@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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