Re: Bug#340236: coreutils: cp -p to nfs destination failsto preserve timestamps

[Brian Dessent]

The Wanderer wrote:

> The strace output does not refer to utimes by name. The relevant EPERM
> is returned by something referred to as SYS_271 - presumably the label
> simply means "strace could not identify the name of this syscall" - and
> all five of the arguments are given only as hex values. Since utimes
> takes only two arguments, I don't think that's what this is. Any idea
> how to figure out what call is being made?

It looks like on x86 linux, 271 is in fact utimes(), according to
<http://www.lxhp.in-berlin.de/lhpsysc0.html>.  The fact that strace
shows 5 arguments is probably because it cannot identify it (and thus
does not know the nature of its arguments), not because it actually has
5.  It is a bit odd that your strace does not identify this -- are you
sure you're using a strace that was compiled against the proper kernel
headers?  It sounds like you're using an old strace with a newer kernel.

Brian