linux-kernel - Re: Atomic non-durable file write API

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] [day] [month] [year] [list]

Message-Id: <20101206090323.6b049846.rdunlap@xenotime.net>
Date:	Mon, 6 Dec 2010 09:03:23 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Olaf van der Spek <olafvdspek@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Atomic non-durable file write API

On Mon, 6 Dec 2010 17:45:23 +0100 Olaf van der Spek wrote:

> On Mon, Nov 29, 2010 at 1:37 PM, Olaf van der Spek <olafvdspek@...il.com> wrote:
> > Hi,
> >
> > Since the introduction of ext4, some apps/users have had issues with
> > file corruption after a system crash. It's not a bug in the FS AFAIK
> > and it's not exclusive to ext4.
> > Writing a temp file, fsync, rename is often proposed. However, the
> > durable aspect of fsync isn't always required and this way has other
> > issues.
> > What is the recommended way for atomic non-durable (complete) file writes?
> >
> > I'm also wondering why FSs commit after open/truncate but before
> > write/close. AFAIK this isn't necessary and thus suboptimal.
> 
> Somebody?
> --

maybe try linux-fsdevel@...r.kernel.org or linux-ext4@...r.kernel.org
mailing lists?

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/