[Bug 199865] out-of-bound write in ext4_init_block_bitmap() when mounting and operating a crafted ext4 image

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=199865

Theodore Tso (tytso@xxxxxxx) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #5 from Theodore Tso (tytso@xxxxxxx) ---
This is triggered by the fact that allocation bitmaps are marked as
uninitialized for block group #0.  Ext4 shouldn't have paid attention to these
flags, since the prerequisite file system feature (uninit_bg or metadata_csum)
was not set.  In addition, even if one of those two feature flags were set,
ext4 should report an file system corruption if bitmaps for bg 0 are marked as
uninitialized and refuse to try to clear those bitmaps, since nothing good can
happen.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux