From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org,
Olga Kornievskaia <olga.kornievskaia@gmail.com>,
Luis Henriques <lhenriques@suse.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH v3 04/13] vfs: remove redundant checks from generic_remap_checks()
Date: Wed, 29 May 2019 11:23:19 -0700 [thread overview]
Message-ID: <20190529182319.GD5231@magnolia> (raw)
In-Reply-To: <20190529174318.22424-5-amir73il@gmail.com>
On Wed, May 29, 2019 at 08:43:08PM +0300, Amir Goldstein wrote:
> The access limit checks on input file range in generic_remap_checks()
> are redundant because the input file size is guaranteied to be within
"guaranteed"...
> limits and pos+len are already checked to be within input file size.
>
> Beyond the fact that the check cannot fail, if it would have failed,
> it could return -EFBIG for input file range error. There is no precedent
> for that. -EFBIG is returned in syscalls that would change file length.
>
> With that call removed, we can fold generic_access_check_limits() into
> generic_write_check_limits().
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Once the changelog is fixed,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> mm/filemap.c | 33 ++++++++++++---------------------
> 1 file changed, 12 insertions(+), 21 deletions(-)
>
> diff --git a/mm/filemap.c b/mm/filemap.c
> index a38619a4a6af..44361928bbb0 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2895,24 +2895,11 @@ EXPORT_SYMBOL(read_cache_page_gfp);
> * LFS limits. If pos is under the limit it becomes a short access. If it
> * exceeds the limit we return -EFBIG.
> */
> -static int generic_access_check_limits(struct file *file, loff_t pos,
> - loff_t *count)
> -{
> - struct inode *inode = file->f_mapping->host;
> - loff_t max_size = inode->i_sb->s_maxbytes;
> -
> - if (!(file->f_flags & O_LARGEFILE))
> - max_size = MAX_NON_LFS;
> -
> - if (unlikely(pos >= max_size))
> - return -EFBIG;
> - *count = min(*count, max_size - pos);
> - return 0;
> -}
> -
> static int generic_write_check_limits(struct file *file, loff_t pos,
> loff_t *count)
> {
> + struct inode *inode = file->f_mapping->host;
> + loff_t max_size = inode->i_sb->s_maxbytes;
> loff_t limit = rlimit(RLIMIT_FSIZE);
>
> if (limit != RLIM_INFINITY) {
> @@ -2923,7 +2910,15 @@ static int generic_write_check_limits(struct file *file, loff_t pos,
> *count = min(*count, limit - pos);
> }
>
> - return generic_access_check_limits(file, pos, count);
> + if (!(file->f_flags & O_LARGEFILE))
> + max_size = MAX_NON_LFS;
> +
> + if (unlikely(pos >= max_size))
> + return -EFBIG;
> +
> + *count = min(*count, max_size - pos);
> +
> + return 0;
> }
>
> /*
> @@ -2963,7 +2958,7 @@ EXPORT_SYMBOL(generic_write_checks);
> /*
> * Performs necessary checks before doing a clone.
> *
> - * Can adjust amount of bytes to clone.
> + * Can adjust amount of bytes to clone via @req_count argument.
> * Returns appropriate error code that caller should return or
> * zero in case the clone should be allowed.
> */
> @@ -3001,10 +2996,6 @@ int generic_remap_checks(struct file *file_in, loff_t pos_in,
> return -EINVAL;
> count = min(count, size_in - (uint64_t)pos_in);
>
> - ret = generic_access_check_limits(file_in, pos_in, &count);
> - if (ret)
> - return ret;
> -
> ret = generic_write_check_limits(file_out, pos_out, &count);
> if (ret)
> return ret;
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-05-29 18:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 17:43 [PATCH v3 00/13] Fixes for major copy_file_range() issues Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 01/13] vfs: introduce generic_copy_file_range() Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 02/13] vfs: no fallback for ->copy_file_range Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 03/13] vfs: introduce generic_file_rw_checks() Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 04/13] vfs: remove redundant checks from generic_remap_checks() Amir Goldstein
2019-05-29 18:23 ` Darrick J. Wong [this message]
2019-05-29 17:43 ` [PATCH v3 05/13] vfs: add missing checks to copy_file_range Amir Goldstein
2019-05-29 18:24 ` Darrick J. Wong
2019-05-29 17:43 ` [PATCH v3 06/13] vfs: introduce file_modified() helper Amir Goldstein
2019-05-29 18:27 ` Darrick J. Wong
2019-05-29 19:08 ` Amir Goldstein
2019-05-29 19:23 ` Amir Goldstein
2019-05-29 21:41 ` Dave Chinner
2019-05-29 17:43 ` [PATCH v3 07/13] xfs: use " Amir Goldstein
2019-05-29 18:31 ` Darrick J. Wong
2019-05-29 19:10 ` Amir Goldstein
2019-05-29 19:13 ` Darrick J. Wong
2019-05-29 17:43 ` [PATCH v3 08/13] vfs: copy_file_range needs to strip setuid bits and update timestamps Amir Goldstein
2019-05-29 18:33 ` Darrick J. Wong
2019-05-29 21:08 ` Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 09/13] ceph: " Amir Goldstein
2019-05-29 19:43 ` Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 10/13] cifs: " Amir Goldstein
2019-05-29 19:36 ` Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 11/13] fuse: " Amir Goldstein
2019-05-29 19:37 ` Amir Goldstein
2019-05-29 20:07 ` Miklos Szeredi
2019-05-29 17:43 ` [PATCH v3 12/13] nfs: " Amir Goldstein
2019-05-29 19:34 ` Amir Goldstein
2019-05-29 20:02 ` Trond Myklebust
2019-05-29 21:00 ` Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 13/13] vfs: allow copy_file_range to copy across devices Amir Goldstein
2019-05-29 20:09 ` Olga Kornievskaia
2019-05-29 21:03 ` Amir Goldstein
2019-06-03 20:39 ` Olga Kornievskaia
2019-06-04 4:11 ` Amir Goldstein
2019-05-29 17:43 ` [PATCH v3 14/13] man-pages: copy_file_range updates Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190529182319.GD5231@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=lhenriques@suse.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=olga.kornievskaia@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).