diff options
| author | Jan Kara <jack@suse.cz> | 2021-01-25 12:05:08 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-01-30 13:32:13 +0100 |
| commit | 9f9623fc9340af731c3f3a09e6e9af0756b38a46 (patch) | |
| tree | d17171b803a325293e406fa55b45284baf7bbd3d /include/trace | |
| parent | 26b30d36cb5cff5e075114d05e5309043514770c (diff) | |
| download | linux-stable-9f9623fc9340af731c3f3a09e6e9af0756b38a46.tar.gz linux-stable-9f9623fc9340af731c3f3a09e6e9af0756b38a46.tar.bz2 linux-stable-9f9623fc9340af731c3f3a09e6e9af0756b38a46.zip | |
writeback: Drop I_DIRTY_TIME_EXPIRE
commit 5fcd57505c002efc5823a7355e21f48dd02d5a51 upstream.
The only use of I_DIRTY_TIME_EXPIRE is to detect in
__writeback_single_inode() that inode got there because flush worker
decided it's time to writeback the dirty inode time stamps (either
because we are syncing or because of age). However we can detect this
directly in __writeback_single_inode() and there's no need for the
strange propagation with I_DIRTY_TIME_EXPIRE flag.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/trace')
| -rw-r--r-- | include/trace/events/writeback.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/trace/events/writeback.h b/include/trace/events/writeback.h index 29d09755e5cf..146e7b3faa85 100644 --- a/include/trace/events/writeback.h +++ b/include/trace/events/writeback.h @@ -20,7 +20,6 @@ {I_CLEAR, "I_CLEAR"}, \ {I_SYNC, "I_SYNC"}, \ {I_DIRTY_TIME, "I_DIRTY_TIME"}, \ - {I_DIRTY_TIME_EXPIRED, "I_DIRTY_TIME_EXPIRED"}, \ {I_REFERENCED, "I_REFERENCED"} \ ) |