diff options
author | Brian Foster <bfoster@redhat.com> | 2022-11-28 18:56:32 +0300 |
---|---|---|
committer | Andrew Morton <akpm@linux-foundation.org> | 2022-12-12 05:12:11 +0300 |
commit | 3cd629e5775397103e0428f62ce64747741dbfe5 (patch) | |
tree | d47475287b33fe570304097a3a6d5dfd4efddbb4 /include | |
parent | feeb9b26952367bc1171592ee476f95aa81ee588 (diff) | |
download | linux-3cd629e5775397103e0428f62ce64747741dbfe5.tar.xz |
mm/fadvise: use LLONG_MAX instead of -1 for eof
generic_fadvise() sets endbyte = -1 to specify end of file (i.e. if
length == 0 is passed from userspace). Most other callers to
filemap_fdatawrite_range() use LLONG_MAX for this purpose, particularly if
they also call fdatawait_range() (which requires end >= start). For
example, sync_file_range(), vfs_fsync() (where the range is passed down
through per-fs ->fsync() callbacks), filemap_flush(), etc.
generic_fadvise() does not currently wait on writeback, but fix the call
up to be consistent with other callers.
Link: https://lkml.kernel.org/r/20221128155632.3950447-3-bfoster@redhat.com
Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions