From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Write is not atomic?
Date: Tue, 16 Oct 2012 01:36:29 +0200 [thread overview]
Message-ID: <7itxtvpate.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <CAMo8Bf+w7S_O2XYin7hnuobpBncZxZBq2=nAQ+Jrszif979xKQ@mail.gmail.com> (Max Filippov's message of "Tue, 16 Oct 2012 02:21:36 +0400")
> You don't check return code here, does write succeed at all?
Yes, both writes return 6.
> Does it ever produce e.g. OuOuilleille
No.
> (as this is what atomicity is about here)?
I was referring to the claim that under Linux writing and adjusting the
file offset are performed as an atomic step, not to the atomicity of the
write operation itself.
-- Juliusz
next prev parent reply other threads:[~2012-10-15 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 21:36 Write is not atomic? Juliusz Chroboczek
2012-10-15 22:21 ` Max Filippov
2012-10-15 23:36 ` Juliusz Chroboczek [this message]
2012-10-15 23:13 ` Dave Chinner
2012-10-15 23:24 ` Philippe Troin
2012-10-15 23:42 ` Max Filippov
2012-10-15 23:40 ` Jochen Striepe
2012-10-16 6:21 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7itxtvpate.fsf@lanthane.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox