From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix utimensat (aka unbreak cp -a)
Date: Tue, 21 Apr 2009 10:36:19 +0200 [thread overview]
Message-ID: <761ea48b0904210136p432bb31dj76ecd09e59b27228@mail.gmail.com> (raw)
In-Reply-To: <878wlufm8s.fsf@lechat.rtp-net.org>
On Tue, Apr 21, 2009 at 10:24 AM, Arnaud Patard
<arnaud.patard@rtp-net.org> wrote:
>
>
> Don't use the glibc function for utimensat because glibc returns -EINVAL
> if the path is null which is a different behaviour with the syscall.
> path can be null because internally the glibc is using utimensat with
> path null (for instance, see __futimes in
> sysdeps/unix/sysv/linux/futimes.c in glibc tree).
>
>
> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
Acked-by: Laurent Desnogues <laurent.desnogues@gmail.com>
next prev parent reply other threads:[~2009-04-21 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 8:24 [Qemu-devel] [PATCH] Fix utimensat (aka unbreak cp -a) Arnaud Patard
2009-04-21 8:36 ` Laurent Desnogues [this message]
2009-04-21 12:34 ` Riku Voipio
2009-04-21 14:42 ` Jamie Lokier
2009-04-21 16:09 ` Martin Mohring
2009-04-21 16:38 ` Martin Mohring
2009-04-21 18:18 ` Riku Voipio
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=761ea48b0904210136p432bb31dj76ecd09e59b27228@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).