linux-kernel - Re: Write is not atomic?

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

Message-ID: <CAMo8Bf+w7S_O2XYin7hnuobpBncZxZBq2=nAQ+Jrszif979xKQ@mail.gmail.com>
Date:	Tue, 16 Oct 2012 02:21:36 +0400
From:	Max Filippov <jcmvbkbc@...il.com>
To:	Juliusz Chroboczek <jch@....jussieu.fr>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Write is not atomic?

On Tue, Oct 16, 2012 at 1:36 AM, Juliusz Chroboczek <jch@....jussieu.fr> wrote:
> Hi,
>
> The Linux manual page for write(2) says:
>
>     The adjustment of the file offset and the write operation are
>     performed as an atomic step.
>
> This is apparently an extension to POSIX, which says
>
>     This volume of IEEE Std 1003.1-2001 does not specify behavior of
>     concurrent writes to a file from multiple processes. Applications
>     should use some form of concurrency control.
>
> The following fragment of code
>
>     int fd;
>     fd = open("exemple", O_CREAT | O_WRONLY | O_TRUNC, 0666);
>     fork();
>     write(fd, "Ouille", 6);

You don't check return code here, does write succeed at all?

>     close(fd);
>
> produces "OuilleOuille", as expected, on ext4 on two machines running
> Linux 3.2 AMD64.  However, over XFS on an old Pentium III at 500 MHz
> running 2.6.32, it produces just "Ouille" roughly once in three times.

Does it ever produce e.g. OuOuilleille (as this is what atomicity is about
here)?

-- 
Thanks.
-- Max
--
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/