This is only an issue for programs compiled against e2fsprogs 1.41 that manipulate bitmaps directly. Fortunately there are very few programs which do that, especially those that try to clear a bitmap. Addresses-Sourceforge-Bugs: #3451486 Reported-by: robi6@xxxxxxxxxxxxxxxxxxxxx Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> --- lib/ext2fs/gen_bitmap64.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/ext2fs/gen_bitmap64.c b/lib/ext2fs/gen_bitmap64.c index 9dbbf9f..4dc4e08 100644 --- a/lib/ext2fs/gen_bitmap64.c +++ b/lib/ext2fs/gen_bitmap64.c @@ -297,8 +297,8 @@ void ext2fs_clear_generic_bmap(ext2fs_generic_bitmap bitmap) { if (EXT2FS_IS_32_BITMAP(bitmap)) ext2fs_clear_generic_bitmap(bitmap); - - bitmap->bitmap_ops->clear_bmap (bitmap); + else + bitmap->bitmap_ops->clear_bmap (bitmap); } int ext2fs_mark_generic_bmap(ext2fs_generic_bitmap bitmap, -- 1.7.4.1.22.gec8e1.dirty -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html