From: Matthew Wilcox <matthew@wil.cx>
To: Jamie Lokier <jamie@shareable.org>
Cc: Rik van Riel <riel@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ray Strode <rstrode@redhat.com>,
elb@psg.com
Subject: Re: RFC: O_PONIES semantics (well O_REWRITE)
Date: Thu, 11 Jun 2009 20:20:28 -0600 [thread overview]
Message-ID: <20090612022028.GB19977@parisc-linux.org> (raw)
In-Reply-To: <20090612020738.GD25550@shareable.org>
On Fri, Jun 12, 2009 at 03:07:38AM +0100, Jamie Lokier wrote:
> > Some of the common failures are:
> > - program overwrites the old config file
> > - program writes a new file, but forgets to fsync before rename
> > - program writes the new file in /tmp, so the rename fails on
> > some systems
> > - program writes a new file and fsyncs, but forgets to give the
> > new file the same file ownership, permission and/or extended
> > attributes as the old file
>
> It's also really hard to do those things from shell scripts, so they
> are almost never done there.
That's a good point, but O_(PONIES|REWRITE) doesn't fix that problem,
since shell scripts can't specify it, and shells can't do it automatically
for all files created.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-06-12 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 1:03 RFC: O_PONIES semantics (well O_REWRITE) Rik van Riel
2009-06-11 5:53 ` Andreas Dilger
2009-06-11 14:06 ` Rik van Riel
2009-06-11 14:23 ` Trond Myklebust
2009-06-11 14:32 ` Ray Strode
2009-06-17 13:52 ` Rik van Riel
2009-06-11 9:51 ` Artem Bityutskiy
2009-06-12 2:07 ` Jamie Lokier
2009-06-12 2:20 ` Matthew Wilcox [this message]
2009-06-12 17:06 ` Ray Strode
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=20090612022028.GB19977@parisc-linux.org \
--to=matthew@wil.cx \
--cc=elb@psg.com \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=rstrode@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).