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
| ||
|
Message-Id: <20200713134448.4CFA3A4051@d06av23.portsmouth.uk.ibm.com> Date: Mon, 13 Jul 2020 19:14:47 +0530 From: Ritesh Harjani <riteshh@...ux.ibm.com> To: Jan Kara <jack@...e.cz>, Ted Tso <tytso@....edu> Cc: linux-ext4@...r.kernel.org, Wolfgang Frisch <wolfgang.frisch@...e.com> Subject: Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents On 7/13/20 6:28 PM, Jan Kara wrote: > From: Wolfgang Frisch <wolfgang.frisch@...e.com> > > When extent tree is corrupted we can hit BUG_ON in > ext4_es_cache_extent(). Check for this and abort caching instead of > crashing the machine. Was it intentionally made corrupted by crafting a corrupted disk image? Are there more such logic in place which checks for such corruption at other places? Maybe a background over the issue which you saw may help. Also how did it recover out of it? Do you think it make sense to still emit a WARN_ON() here and then return which warns that this could possibly a corrupted extent entry? (maybe WARN_ON_ONCE() or via some ratelimiting if multiple extent entries are corrupted for that inode). -ritesh
Powered by blists - more mailing lists