Skip to content

Commit 45cbce5

Browse files
Christoph Hellwigbrauner
authored andcommitted
mm: remove __filemap_fdatawrite_range
Use filemap_fdatawrite_range and filemap_fdatawrite_range_kick instead of the low-level __filemap_fdatawrite_range that requires the caller to know the internals of the writeback_control structure and remove __filemap_fdatawrite_range now that it is trivial and only two callers would be left. Signed-off-by: Christoph Hellwig <hch@lst.de> Link: https://patch.msgid.link/20251024080431.324236-10-hch@lst.de Reviewed-by: Jan Kara <jack@suse.cz> Reviewed-by: Damien Le Moal <dlemoal@kernel.org> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Christian Brauner <brauner@kernel.org>
1 parent 1bcb413 commit 45cbce5

4 files changed

Lines changed: 13 additions & 28 deletions

File tree

fs/sync.c

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -280,14 +280,13 @@ int sync_file_range(struct file *file, loff_t offset, loff_t nbytes,
280280
}
281281

282282
if (flags & SYNC_FILE_RANGE_WRITE) {
283-
int sync_mode = WB_SYNC_NONE;
284-
285283
if ((flags & SYNC_FILE_RANGE_WRITE_AND_WAIT) ==
286284
SYNC_FILE_RANGE_WRITE_AND_WAIT)
287-
sync_mode = WB_SYNC_ALL;
288-
289-
ret = __filemap_fdatawrite_range(mapping, offset, endbyte,
290-
sync_mode);
285+
ret = filemap_fdatawrite_range(mapping, offset,
286+
endbyte);
287+
else
288+
ret = filemap_fdatawrite_range_kick(mapping, offset,
289+
endbyte);
291290
if (ret < 0)
292291
goto out;
293292
}

include/linux/pagemap.h

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,6 @@ static inline int filemap_fdatawait(struct address_space *mapping)
5454
bool filemap_range_has_page(struct address_space *, loff_t lstart, loff_t lend);
5555
int filemap_write_and_wait_range(struct address_space *mapping,
5656
loff_t lstart, loff_t lend);
57-
int __filemap_fdatawrite_range(struct address_space *mapping,
58-
loff_t start, loff_t end, int sync_mode);
5957
int filemap_fdatawrite_range(struct address_space *mapping,
6058
loff_t start, loff_t end);
6159
int filemap_check_errors(struct address_space *mapping);

mm/fadvise.c

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,7 @@ int generic_fadvise(struct file *file, loff_t offset, loff_t len, int advice)
111111
spin_unlock(&file->f_lock);
112112
break;
113113
case POSIX_FADV_DONTNEED:
114-
__filemap_fdatawrite_range(mapping, offset, endbyte,
115-
WB_SYNC_NONE);
114+
filemap_fdatawrite_range_kick(mapping, offset, endbyte);
116115

117116
/*
118117
* First and last FULL page! Partial pages are deliberately

mm/filemap.c

Lines changed: 7 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -392,32 +392,23 @@ static int filemap_writeback(struct address_space *mapping, loff_t start,
392392
}
393393

394394
/**
395-
* __filemap_fdatawrite_range - start writeback on mapping dirty pages in range
395+
* filemap_fdatawrite_range - start writeback on mapping dirty pages in range
396396
* @mapping: address space structure to write
397397
* @start: offset in bytes where the range starts
398398
* @end: offset in bytes where the range ends (inclusive)
399-
* @sync_mode: enable synchronous operation
400399
*
401400
* Start writeback against all of a mapping's dirty pages that lie
402401
* within the byte offsets <start, end> inclusive.
403402
*
404-
* If sync_mode is WB_SYNC_ALL then this is a "data integrity" operation, as
405-
* opposed to a regular memory cleansing writeback. The difference between
406-
* these two operations is that if a dirty page/buffer is encountered, it must
407-
* be waited upon, and not just skipped over.
403+
* This is a data integrity operation that waits upon dirty or in writeback
404+
* pages.
408405
*
409406
* Return: %0 on success, negative error code otherwise.
410407
*/
411-
int __filemap_fdatawrite_range(struct address_space *mapping, loff_t start,
412-
loff_t end, int sync_mode)
413-
{
414-
return filemap_writeback(mapping, start, end, sync_mode, NULL);
415-
}
416-
417408
int filemap_fdatawrite_range(struct address_space *mapping, loff_t start,
418409
loff_t end)
419410
{
420-
return __filemap_fdatawrite_range(mapping, start, end, WB_SYNC_ALL);
411+
return filemap_writeback(mapping, start, end, WB_SYNC_ALL, NULL);
421412
}
422413
EXPORT_SYMBOL(filemap_fdatawrite_range);
423414

@@ -441,7 +432,7 @@ EXPORT_SYMBOL(filemap_fdatawrite);
441432
int filemap_fdatawrite_range_kick(struct address_space *mapping, loff_t start,
442433
loff_t end)
443434
{
444-
return __filemap_fdatawrite_range(mapping, start, end, WB_SYNC_NONE);
435+
return filemap_writeback(mapping, start, end, WB_SYNC_NONE, NULL);
445436
}
446437
EXPORT_SYMBOL_GPL(filemap_fdatawrite_range_kick);
447438

@@ -689,8 +680,7 @@ int filemap_write_and_wait_range(struct address_space *mapping,
689680
return 0;
690681

691682
if (mapping_needs_writeback(mapping)) {
692-
err = __filemap_fdatawrite_range(mapping, lstart, lend,
693-
WB_SYNC_ALL);
683+
err = filemap_fdatawrite_range(mapping, lstart, lend);
694684
/*
695685
* Even if the above returned error, the pages may be
696686
* written partially (e.g. -ENOSPC), so we wait for it.
@@ -792,8 +782,7 @@ int file_write_and_wait_range(struct file *file, loff_t lstart, loff_t lend)
792782
return 0;
793783

794784
if (mapping_needs_writeback(mapping)) {
795-
err = __filemap_fdatawrite_range(mapping, lstart, lend,
796-
WB_SYNC_ALL);
785+
err = filemap_fdatawrite_range(mapping, lstart, lend);
797786
/* See comment of filemap_write_and_wait() */
798787
if (err != -EIO)
799788
__filemap_fdatawait_range(mapping, lstart, lend);

0 commit comments

Comments
 (0)