[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uximFUoL3-ovymF=jX=w-xy8Kf-B9=eJvJ9TZG=0spxwnQ@mail.gmail.com>
Date: Sat, 25 Apr 2020 11:54:25 +0300
From: Amir Goldstein <amir73il@...il.com>
To: Ritesh Harjani <riteshh@...ux.ibm.com>
Cc: Ext4 <linux-ext4@...r.kernel.org>, Jan Kara <jack@...e.cz>,
Theodore Tso <tytso@....edu>,
Andreas Dilger <adilger@...ger.ca>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Christoph Hellwig <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>,
Murphy Zhou <jencce.kernel@...il.com>,
Miklos Szeredi <miklos@...redi.hu>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
overlayfs <linux-unionfs@...r.kernel.org>
Subject: Re: [PATCH 4/5] overlayfs: Check for range bounds before calling i_op->fiemap()
On Thu, Apr 23, 2020 at 1:48 PM Ritesh Harjani <riteshh@...ux.ibm.com> wrote:
>
> Underlying fs may not be able to handle the length in fiemap
> beyond sb->s_maxbytes. So similar to how VFS ioctl does it,
> add fiemap_check_ranges() check in ovl_fiemap() as well
> before calling underlying fs i_op->fiemap() call.
>
> Signed-off-by: Ritesh Harjani <riteshh@...ux.ibm.com>
> ---
> fs/overlayfs/inode.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/overlayfs/inode.c b/fs/overlayfs/inode.c
> index 79e8994e3bc1..9bcd2e96faad 100644
> --- a/fs/overlayfs/inode.c
> +++ b/fs/overlayfs/inode.c
> @@ -455,16 +455,21 @@ static int ovl_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
> int err;
> struct inode *realinode = ovl_inode_real(inode);
> const struct cred *old_cred;
> + u64 length;
To be more clear, I would call that reallen, but apart from that, you may add:
Reviewed-by: Amir Goldstein <amir73il@...il.com>
Thanks,
Amir.
Powered by blists - more mailing lists