linux-ext4 - question about fsync

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

Message-ID: <AANLkTinFkS1Uf+GJT+SE43KpqoUWyJERBFTzxKyLgX+u@mail.gmail.com>
Date:	Mon, 25 Oct 2010 12:49:36 +0100
From:	Filipe David Manana <fdmanana@...che.org>
To:	linux-ext4@...r.kernel.org
Subject: question about fsync

Hi,

I've recently seen code that does the following:

- opens a file (write append mode) and writes data to it
- opens a 2nd file descriptor for that same file (write append mode as
well) and does an fsync call on this 2nd file descriptor
- closes the 2nd file descriptor
- continues writing to the 1st file descriptor
- etc

Is there a risk that some of the data might not get fsynced to disk? I
mean, is it possible that the 2nd file descriptor doesn't have all the
same metadata as the first one?

Thanks.

-- 
Filipe David Manana,
fdmanana@...il.com, fdmanana@...che.org

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."
--
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