linux-kernel - Re: [f2fs-dev] [PATCH v5] f2fs: reduce expensive checkpoint trigger frequency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <37db0df5-c39c-4ddf-a0e2-207ad95857a5@kernel.org>
Date: Tue, 9 Jul 2024 17:55:28 +0800
From: Chao Yu <chao@...nel.org>
To: wangzijie <wangzijie1@...or.com>
Cc: jaegeuk@...nel.org, linux-f2fs-devel@...ts.sourceforge.net,
 linux-kernel@...r.kernel.org, zhiguo.niu@...soc.com, bintian.wang@...or.com
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: reduce expensive checkpoint trigger
 frequency

On 2024/7/9 16:40, wangzijie wrote:
> Hi Chao,
> I think that we should call f2fs_remove_ino_entry in f2fs_evict_inode to delete
> ino_entry in CP_XATTR_DIR list.

wangzijie,

For the case:
- update parent's xattr
- flush parent's metadata to disk
- evict parent's inode
- fsync child  --- we should trigger checkpoint to persist parent's
xattr in checkpoint?