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
| ||
|
Date: Fri, 7 Oct 2022 07:22:46 -0700 From: Daeho Jeong <daeho43@...il.com> To: Chao Yu <chao@...nel.org> Cc: linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, kernel-team@...roid.com, Daeho Jeong <daehojeong@...gle.com> Subject: Re: [f2fs-dev] [PATCH v4 1/2] f2fs: correct i_size change for atomic writes > > Fine to me. > > But another question is, now it allows GC to migrate blocks belong > to atomic files, so, during migration, it may update extent cache, > once largest extent was updated, it will mark inode dirty, but after > this patch, it may lose the extent change? thoughts? > Oh, I missed that case. Maybe we could prevent updating the i_size of atomic files in f2fs_update_inode() while allowing inode dirtying.
Powered by blists - more mailing lists