Email List: Xaustin-group-lX
[All Lists]

Re: Bug in XSHd5 futimens

To: Geoff Clare <gwc@xxxxxxxxxxxxx>
Subject: Re: Bug in XSHd5 futimens
From: Michael Kerrisk <mtk.lists@xxxxxxxxx>
Date: Sun, 18 May 2008 23:09:04 +0200
Cc: austin-group-l@xxxxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=EIqluGfSgcRdz5OCOF4jlk9A5Ce/xtOR17xJROBdhG0=; b=RNmL0ZpPGBoL6iUDpGvBwcn+0HmD2Sj6EdjtHwLaA6E21IihTIu3hjzJRWiR+aOOPLI54cE+4W08BK0igQfr0A66HvodsEMB7Eogvj8ZhLKfLkSnDRrSfH3PC/VepARIg3RbQMIU7EC+/hTWa3zs5lcFDOspZQeaGU+K//f24R8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=r1Sgg803uxddYyFimvphoAOeiBuvltgYEDp79CL9WeBx6C+W2Sx6Xyv187HeFy6S2flr8ExmsdimpHA0+OQn9oexgqNq8Kgtitgo9gJi46nNHvOjem9P609HeOfQDlluWLn9TtnjEM9ihNgcE1NR1C7A9QFBQMSLLsRmTKh+YtA=
References: <200805142143.WAA17994@xoneweb.opengroup.org> <20080515092607.GA21034@squonk.masqnet> <482C06F2.9050107@gmail.com> <20080516085908.GA1785@squonk.masqnet>
Geoff Clare wrote:
Michael Kerrisk <mtk.lists@gmail.com> wrote, on 15 May 2008:
Geoff Clare wrote:
Michael Kerrisk <michael.kerrisk@gmail.com> wrote, on 14 May 2008:
@ page 969 line 32433 section futimens comment {utimensat-errs}

I agree that this change is needed. Since draft 5.1 has already been
produced, I suggest that we should take this as an aardvark against 5.1
(the page and line numbers are the same), to be addressed in TC1.
Do I need to do anything to get that Aardvark moved to the TC1 queue?
You don't need to do anything.  As per the minutes of yesterday's
teleconference, Andrew is going to create a new set of aardvarks for
the revision and yours will be the first entry.

In passing, does anyone know what the rationale was for having two different permission errors (EACCES and EPERM) for utime() and utimes() (and thus now utimesat() and futimens())? Was this just standardization of existing practice, or is there another reason?
I'm fairly sure it was just existing practice.
I see that the POSIX.1-2004 utimes() spec carries a similar mistake -- I guess that's where the working for utimenssat() came from. Should I raise a separate Aardvark to get that fixed?

Cheers,

Michael


<Prev in Thread] Current Thread [Next in Thread>