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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 17 Nov 2018 16:29:12 +0900 From: Eiichi Tsukata <devel@...ukata.com> To: andi@...stfloor.org Cc: "Theodore Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [RFC PATCH 0/1] fs: fix race between llseek SEEK_END and write > > > > Q2. If it is a bug, how should we fix it? > > > > Currently I'm planning to re-introduce generic_file_llseek_unlocked() > > and inode lock in generic_file_llseek() for SEEK_END. Then replace > > generic_file_llseek() with generic_file_llseek_unlocked() if it called > > with inode lock in individual file systems. Please let me know if the > > way is not appropreate or any other better way to fix it. > > Sounds reasonable. > > -Andi Thanks for comments. I'll make a patch. Eiichi
Powered by blists - more mailing lists