summaryrefslogtreecommitdiff
path: root/include/trace/events
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2020-05-29 16:24:43 +0200
committerJan Kara <jack@suse.cz>2020-06-15 09:18:46 +0200
commit5fcd57505c002efc5823a7355e21f48dd02d5a51 (patch)
tree3841b53ef7831553de2c7bf40b3c673f1fd263b4 /include/trace/events
parentf9cae926f35e8230330f28c7b743ad088611a8de (diff)
downloadlinux-next-5fcd57505c002efc5823a7355e21f48dd02d5a51.tar.gz
writeback: Drop I_DIRTY_TIME_EXPIRE
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>
Diffstat (limited to 'include/trace/events')
-rw-r--r--include/trace/events/writeback.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/trace/events/writeback.h b/include/trace/events/writeback.h
index 7565dcd59697..e7cbccc7c14c 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"} \
)