| 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
| ||
|
Message-ID: <20090329130251.GF15492@elf.ucw.cz> Date: Sun, 29 Mar 2009 15:02:51 +0200 From: Pavel Machek <pavel@....cz> To: Artem Bityutskiy <Artem.Bityutskiy@...ia.com> Cc: Artem Bityutskiy <dedekind@...dex.ru>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: replace() system call needed (was Re: EXT4-ish "fixes" in UBIFS) On Sun 2009-03-29 16:00:45, Artem Bityutskiy wrote: > Pavel Machek wrote: >>>>> 2. create/write/rename leads to empty files >>>> ..but this should not be. If we want to make that explicit, we should >>>> provide "replace()" operation; where replace is rename that makes sure >>>> that source file is completely on media before commiting the rename. >>> Well, OK, we can fsync() before rename, we just need clean rules >>> for this, so that all Linux FSes would follow them. Would be nice >>> to have final agreement on all this stuff. >> >> My proposal is >> >> rename() stays. > > It stays and: > > 1. does _not_ fsync Does not fsync. If someone wants to make sure one of the files is on the disk, he should use replace(). [On non-linux systems, replace() should be implemented as fsync/rename in libc or something.] Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists