btrfs: add ability to change features via sysfs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 29 lines · Linux Kernel
Gitweb: http://git.kernel.org/linus/;a=commit;h=ba631941ef09c10e229661219dbd1707e56131d8 Commit: ba631941ef09c10e229661219dbd1707e56131d8 Parent: 79da4fa4d9dcf8c948ef8b5848f747ef08f6e732 Author: Jeff Mahoney <[email protected]> AuthorDate: Fri Nov 1 13:07:01 2013 -0400 Committer: Chris Mason <[email protected]> CommitDate: Tue Jan 28 13:19:27 2014 -0800btrfs: add ability to change features via sysfs
(quoted diff) +18
-0+static int can_modify_feature(struct btrfs_feature_attr *fa) +{ + int val = 0; + u64 set, clear; + switch (fa->feature_set) { + case FEAT_COMPAT: + set = BTRFS_FEATURE_COMPAT_SAFE_SET; + clear = BTRFS_FEATURE_COMPAT_SAFE_CLEAR; + break; + case FEAT_COMPAT_RO: + set = BTRFS_FEATURE_COMPAT_RO_SAFE_SET; + clear = BTRFS_FEATURE_COMPAT_RO_SAFE_CLEAR; + break; + case FEAT_INCOMPAT: + set = BTRFS_FEATURE_INCOMPAT_SAFE_SET; + clear = BTRFS_FEATURE_INCOMPAT_SAFE_CLEAR; + break; + default:
Review
Quoted 10 lines
(quoted diff) +10
-0+ BUG(); + } + + if (set & fa->feature_bit) + val |= 1; + if (clear & fa->feature_bit) + val |= 2; + + return val; +}
Coverity flagged 9 new issues in btrfs last night.
It flagged this (and a bunch of similar areas) because the CLEAR defines are 0.
Doing if (0 & fa->feature_bit) is always going to be false.
There's 72 other btrfs bugs at http://scan.coverity.com (twice that of say, ext* or xfs). Many of them look real, though some look complicated enough that they really need someone familiar with how btrfs works to know "can't happen". If some of you want to sign up, I can get the access approved quickly.
thanks,
Dave