| 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: <AANLkTinaAtrCYfusv59T3FE5A45A77R8oTMPpJUJs03p@mail.gmail.com> Date: Sun, 26 Dec 2010 17:02:33 +0100 From: Olaf van der Spek <olafvdspek@...il.com> To: Boaz Harrosh <bharrosh@...asas.com> Cc: Nick Piggin <npiggin@...il.com>, "Ted Ts'o" <tytso@....edu>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-ext4@...r.kernel.org Subject: Re: Atomic non-durable file write API On Sun, Dec 26, 2010 at 4:55 PM, Boaz Harrosh <bharrosh@...asas.com> wrote: > What if you use a soft link? wouldn't that solve all of your problems? > > - do your fsync/fdatasync of choice in a *backend thread* then at the return > - point set to the new link, fsync the link it's very small, therefore fast. > - Then delete the old source file. > > You need a simple "name-version" schema and the "name" is kept soft linked. > (You might even skip the last step above and implement an undo stack, some > background management caps on history size) > >>> >>>> and this way has other >>>> issues, like losing file meta-data. >>> > > With soft links this is persevered? > > Same system can be used with lots of files. where the final switch is > the set of a single soft-link say to a folder of related files. Are you proposing to turn every single file into a symlink? How would that solve the meta-data issue? Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists