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: <20200521060833.855415204F@d06av21.portsmouth.uk.ibm.com> Date: Thu, 21 May 2020 11:38:32 +0530 From: Ritesh Harjani <riteshh@...ux.ibm.com> To: Murphy Zhou <jencce.kernel@...il.com> Cc: linux-ext4@...r.kernel.org, jack@...e.cz, tytso@....edu, adilger@...ger.ca, darrick.wong@...cle.com, hch@...radead.org, Alexander Viro <viro@...iv.linux.org.uk>, Dan Carpenter <dan.carpenter@...cle.com>, "Aneesh Kumar K . V" <aneesh.kumar@...ux.ibm.com>, Miklos Szeredi <miklos@...redi.hu>, Amir Goldstein <amir73il@...il.com>, linux-fsdevel@...r.kernel.org, linux-unionfs@...r.kernel.org Subject: Re: [PATCH 0/5] ext4/overlayfs: fiemap related fixes Hello Murphy, On 5/19/20 8:13 AM, Murphy Zhou wrote: > On Thu, Apr 23, 2020 at 04:17:52PM +0530, Ritesh Harjani wrote: >> Hello All, >> >> Here are some changes, which as I understand, takes the right approach in fixing >> the offset/length bounds check problem reported in threads [1]-[2]. >> These warnings in iomap_apply/ext4 path are reported after ext4_fiemap() >> was moved to use iomap framework and when overlayfs is mounted on top of ext4. >> Though the issues were identified after ext4 moved to iomap framework, but >> these changes tries to fix the problem which are anyways present in current code >> irrespective of ext4 using iomap framework for fiemap or not. > > Ping? It's superseded by below mentioned patch series. Please follow below thread. https://lore.kernel.org/linux-ext4/20200520032837.GA2744481@mit.edu/T/#t -ritesh
Powered by blists - more mailing lists