diff options
| author | Josef Bacik <jbacik@fusionio.com> | 2013-08-26 16:53:15 -0400 |
|---|---|---|
| committer | Chris Mason <chris.mason@fusionio.com> | 2013-09-01 08:16:32 -0400 |
| commit | 2e17c7c65e5dcbb53a6384a3406244f62bca189c (patch) | |
| tree | 9c4c368a46a5e34b4406ad9d5f966596f35b834f /fs/btrfs/Kconfig | |
| parent | 726551ebc79c0a41f66376463ebe8c84c89c1151 (diff) | |
| download | linux-2e17c7c65e5dcbb53a6384a3406244f62bca189c.tar.bz2 | |
Btrfs: add support for asserts
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,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'fs/btrfs/Kconfig')
| -rw-r--r-- | fs/btrfs/Kconfig | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig index 2b3b83296977..398cbd517be2 100644 --- a/fs/btrfs/Kconfig +++ b/fs/btrfs/Kconfig @@ -72,3 +72,12 @@ config BTRFS_DEBUG performance, or export extra information via sysfs. If unsure, say N. + +config BTRFS_ASSERT + bool "Btrfs assert support" + depends on BTRFS_FS + help + Enable run-time assertion checking. This will result in panics if + any of the assertions trip. This is meant for btrfs developers only. + + If unsure, say N. |