[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200522045615.y3vhtfdbmpndzwvp@xzhoux.usersys.redhat.com>
Date: Fri, 22 May 2020 12:56:15 +0800
From: Murphy Zhou <jencce.kernel@...il.com>
To: Ritesh Harjani <riteshh@...ux.ibm.com>
Cc: Murphy Zhou <jencce.kernel@...il.com>, 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
Hi Ritesh,
On Thu, May 21, 2020 at 11:38:32AM +0530, Ritesh Harjani wrote:
> 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
Great. Thanks for the info!
>
> -ritesh
--
Murphy
Powered by blists - more mailing lists