summaryrefslogtreecommitdiffstats
path: root/fs/namei.c
diff options
context:
space:
mode:
authorJingbo Xu <jefflexu@linux.alibaba.com>2023-10-14 20:55:11 +0800
committerChristian Brauner <brauner@kernel.org>2023-10-19 11:03:16 +0200
commit6654408a33e6297d8e1d2773409431d487399b95 (patch)
tree8384645ea91e1eb0a81298558f95593b41c5bd3d /fs/namei.c
parente311ba29a552194ece6c1579fe434bdad550bfac (diff)
downloadlinux-6654408a33e6297d8e1d2773409431d487399b95.tar.gz
linux-6654408a33e6297d8e1d2773409431d487399b95.tar.bz2
linux-6654408a33e6297d8e1d2773409431d487399b95.zip
writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs
The cgwb cleanup routine will try to release the dying cgwb by switching the attached inodes. It fetches the attached inodes from wb->b_attached list, omitting the fact that inodes only with dirty timestamps reside in wb->b_dirty_time list, which is the case when lazytime is enabled. This causes enormous zombie memory cgroup when lazytime is enabled, as inodes with dirty timestamps can not be switched to a live cgwb for a long time. It is reasonable not to switch cgwb for inodes with dirty data, as otherwise it may break the bandwidth restrictions. However since the writeback of inode metadata is not accounted for, let's also switch inodes with dirty timestamps to avoid zombie memory and block cgroups when laztytime is enabled. Fixes: c22d70a162d3 ("writeback, cgroup: release dying cgwbs by switching attached inodes") Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com> Link: https://lore.kernel.org/r/20231014125511.102978-1-jefflexu@linux.alibaba.com Acked-by: Tejun Heo <tj@kernel.org> Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/namei.c')
0 files changed, 0 insertions, 0 deletions