From: Jeff Mahoney <jeffm@suse.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Zach Brown <zab@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add support for asserts
Date: Tue, 27 Aug 2013 15:23:17 -0400 [thread overview]
Message-ID: <521CFCA5.6000007@suse.com> (raw)
In-Reply-To: <20130827134736.GJ29654@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
On 8/27/13 9:47 AM, Josef Bacik wrote:
> On Mon, Aug 26, 2013 at 02:53:26PM -0700, Zach Brown wrote:
>>> 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.
>>
>> I like the sound of that!
>>
>>> --- a/fs/btrfs/ctree.h
>>> +++ b/fs/btrfs/ctree.h
>>> @@ -3814,6 +3814,22 @@ void btrfs_printk(const struct btrfs_fs_info *fs_info, const char *fmt, ...)
>>> #define btrfs_debug(fs_info, fmt, args...) \
>>> btrfs_printk(fs_info, KERN_DEBUG fmt, ##args)
>>>
>>> +#ifdef BTRFS_ASSERT
>>> +
>>> +static inline void assfail(char *expr, char *file, int lin)
>>> +{
>>> + printk(KERN_ERR "BTRFS assertion failed: %s, file: %s, line: %d",
>>> + expr, file, line);
>>> + BUG();
>>> +}
>>
>> I'm not sure why this is needed.
>>
>>> +#define ASSERT(expr) \
>>> + (unlikely(expr) ? (void)0 : assfail(#expr, __FILE__, __LINE__))
>>
>> (Passing the assertion is unlikely()? I know, this is from xfs...
>> still.)
>>
>
> Yeah I copy+pasted and then thought about it after I sent it. I will fix it up.
>
>>> +#else
>>> +#define ASSERT(expr) ((void)0)
>>> +#endif
>>
>> Anyway, if you're going to do it this way, why not:
>>
>> #ifdef BTRFS_ASSERT
>> #define btrfs_assert(cond) BUG_ON(!(cond))
>> #else
>> #define btrfs_assert(cond) do { if (cond) ; } while (0)
>> #endif
>>
>
> I like the verbosity, especially with random kernel versions and such, it will
> help me figure out where we BUG_ON()'ed without having to checkout a particular
> version and go hunting. Thanks,
Agreed. One of the positives of the obnoxious reiserfs warning IDs is
that it uniquely identifies a call site across kernel versions. You can
tell at a glance that it's the same failure you may have been chasing
for a while. Anything to make the ID-at-a-glance easy is worth it.
-Jeff
--
Jeff Mahoney
SUSE Labs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2013-08-27 19:23 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 [this message]
2013-08-27 19:28 ` Jeff Mahoney
2013-08-27 20:56 ` Josef Bacik
2013-08-27 21:07 ` Jeff Mahoney
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=521CFCA5.6000007@suse.com \
--to=jeffm@suse.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.