Re: [PATCH] ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max

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

 



On Mon, Apr 20, 2020 at 07:39:59PM -0700, Harshad Shirwadkar wrote:
> If eh->eh_max is 0, EXT_MAX_EXTENT/INDEX would evaluate to unsigned
> (-1) resulting in illegal memory accesses. Although there is no
> consistent repro, we see that generic/019 sometimes crashes because of
> this bug.
> 
> Ran gce-xfstests smoke and verified that there were no regressions.
> 
> Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@xxxxxxxxx>

Applied, thanks.

					- Ted



[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