From: Jamie Lokier <jamie@shareable.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
drepper@redhat.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] utimensat() non-conformances and fixes [v3]
Date: Tue, 3 Jun 2008 13:10:15 +0100 [thread overview]
Message-ID: <20080603121015.GC28905@shareable.org> (raw)
In-Reply-To: <20080603120850.GZ28946@ZenIV.linux.org.uk>
Al Viro wrote:
> On Tue, Jun 03, 2008 at 01:01:35PM +0100, Jamie Lokier wrote:
> > > with a lot of things, starting with "why utimes(2) has weaker requirements
> > > with NULL argument", but we are far too late to fix that.
> >
> > To be fair, having a writable file descriptor only lets you change the
> > mtime to "now", and having a readable file descriptor only lets you
> > change the atime to "now".
> >
> > Changing the times _in general_ can be seen as over-reaching those
> > capabilities and arguably justifies more strict checks.
>
> Which is what all questions about writability apply only to NULL case
> anyway...
Oh!
So if I have the file descriptor, I can just as well change the mtime
by read a byte and write it back. Or even do a zero-length write, on
some OSes.
-- Jamie
next prev parent reply other threads:[~2008-06-03 12:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 8:31 [PATCH] utimensat() non-conformances and fixes -- version 2 Michael Kerrisk
2008-05-16 8:34 ` Michael Kerrisk
2008-05-16 16:59 ` Miklos Szeredi
2008-05-17 19:57 ` Michael Kerrisk
2008-05-19 9:50 ` Miklos Szeredi
2008-05-19 10:12 ` Miklos Szeredi
2008-05-19 12:24 ` Michael Kerrisk
2008-05-19 13:17 ` Miklos Szeredi
2008-05-30 15:34 ` [PATCH] utimensat() non-conformances and fixes [v3] Michael Kerrisk
2008-05-30 16:37 ` Miklos Szeredi
2008-05-30 18:24 ` Michael Kerrisk
2008-05-30 19:22 ` Miklos Szeredi
2008-05-30 19:32 ` Matthew Wilcox
2008-05-30 20:08 ` Miklos Szeredi
2008-05-30 19:43 ` Michael Kerrisk
2008-05-30 20:17 ` Miklos Szeredi
2008-05-31 5:28 ` Michael Kerrisk
2008-05-30 20:17 ` Andrew Morton
2008-05-31 5:44 ` Michael Kerrisk
2008-06-03 11:05 ` Michael Kerrisk
2008-06-03 11:13 ` Miklos Szeredi
2008-06-03 11:22 ` Al Viro
2008-06-03 11:27 ` Michael Kerrisk
2008-06-03 11:30 ` Jamie Lokier
2008-06-03 11:39 ` Michael Kerrisk
2008-06-03 11:49 ` Al Viro
2008-06-03 11:58 ` Al Viro
2008-06-03 12:01 ` Jamie Lokier
2008-06-03 12:08 ` Al Viro
2008-06-03 12:10 ` Jamie Lokier [this message]
2008-06-03 12:16 ` Miklos Szeredi
2008-06-03 13:05 ` Al Viro
2008-06-03 11:52 ` Michael Kerrisk
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=20080603121015.GC28905@shareable.org \
--to=jamie@shareable.org \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mtk.manpages@googlemail.com \
--cc=viro@ZenIV.linux.org.uk \
/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