linux-ext4 - Re: [PATCH] ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200514144941.GT1596452@mit.edu>
Date:   Thu, 14 May 2020 10:49:41 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Harshad Shirwadkar <harshadshirwadkar@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max

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@...il.com>

Applied, thanks.

					- Ted