Brian Foster 3cd629e577 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>
2022-12-11 18:12:11 -08:00
..
2022-11-30 15:58:53 -08:00
2021-05-05 11:27:24 -07:00
2022-12-11 18:12:09 -08:00
2022-12-11 18:12:08 -08:00
2022-09-26 19:46:16 -07:00
2022-11-30 15:58:54 -08:00
2022-03-23 18:03:08 -07:00
2022-10-03 14:03:04 -07:00
2022-12-11 18:12:08 -08:00
2022-10-03 14:02:43 -07:00
2022-09-26 19:46:09 -07:00
2022-09-26 19:46:28 -07:00
2022-09-26 19:46:26 -07:00
2021-05-07 00:26:35 -07:00
2022-11-30 15:58:46 -08:00
2022-12-11 18:12:10 -08:00
2022-12-11 18:12:10 -08:00
2022-12-11 18:12:10 -08:00