Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add support for asserts
Date: Tue, 27 Aug 2013 17:07:11 -0400	[thread overview]
Message-ID: <521D14FF.9090604@suse.com> (raw)
In-Reply-To: <20130827205637.GM29654@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

On 8/27/13 4:56 PM, Josef Bacik wrote:
> On Tue, Aug 27, 2013 at 03:28:24PM -0400, Jeff Mahoney wrote:
>> On 8/26/13 4:56 PM, Josef Bacik wrote:
>>> One of the complaints we get a lot is how many BUG_ON()'s we have.  So to help
>>> with this I'm introducing a kconfig option to enable/disable a new ASSERT()
>>> mechanism much like what XFS does.  This will allow us developers to still get
>>> our nice panics but allow users/distros to compile them out.  With this we can
>>> go through and convert any BUG_ON()'s that we have to catch actual programming
>>> mistakes to the new ASSERT() and then fix everybody else to return errors.  This
>>> will also allow developers to leave sanity checks in their new code to make sure
>>> we don't trip over problems while testing stuff and vetting new features.
>>> Thanks,
>>
>> I don't think the complaint is so much about the number of BUG_ONs, but
>> that there's no distinction between something that is supposed to be
>> impossible and something that is improbable. The BUG_ONs to keep code
>> correctness are good and are littered all over the kernel with positive
>> results. The BUG_ONs that are there in place of real error handling
>> served their purpose and need to be replaced.
>>
>> So, I don't know if it's a net win to compile the "good" BUG_ONs out of
>> the code. Especially if a user runs into something strange yet familiar
>> and the first response is "oh, huh, can you rebuild with asserts enabled?"
>>
> 
> Either I provide an option for it or distros do it themselves, this cuts out the
> middle man.  I'd really rather they just be on all the time since they aren't
> things we should hit anyway, but at least this way people have a choice.

Ok. With my distro hat on, I can tell you I'll be leaving them on. :)

-Jeff


-- 
Jeff Mahoney
SUSE Labs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]

  reply	other threads:[~2013-08-27 21:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 20:56 [PATCH] Btrfs: add support for asserts Josef Bacik
2013-08-26 21:21 ` Eric Sandeen
2013-08-26 21:53 ` Zach Brown
2013-08-26 22:02   ` Eric Sandeen
2013-08-26 22:09     ` Zach Brown
2013-08-27 13:47   ` Josef Bacik
2013-08-27 19:23     ` Jeff Mahoney
2013-08-27 19:28 ` Jeff Mahoney
2013-08-27 20:56   ` Josef Bacik
2013-08-27 21:07     ` Jeff Mahoney [this message]
2013-08-27 21:21       ` Eric Sandeen
2013-08-27 21:25         ` Jeff Mahoney
2013-08-27 21:28           ` Eric Sandeen
2013-08-27 21:38             ` Jeff Mahoney
2013-08-28 16:32 ` David Sterba

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=521D14FF.9090604@suse.com \
    --to=jeffm@suse.com \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@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