qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@raisama.net>
To: "Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Wed, 10 Jun 2009 16:10:33 -0300	[thread overview]
Message-ID: <1244659259-sup-8660@blackpad> (raw)
In-Reply-To: <87bpownof6.fsf@lechat.rtp-net.org>

Excerpts from Arnaud Patard (Rtp)'s message of Wed Jun 10 11:39:25 -0300 2009:
> Eduardo Habkost <ehabkost@redhat.com> writes:
<snip>
> >> 
> >> afaik, they can also be found in maemo's qemu git tree (and sent again
> >> later to the mailing list)
> >
> > Why is it not included, if it is a better fix?
> 
> I don't have the reason, only guesses. It looks like linux-user is
> getting a lot less attention than full system emulation, which makes
> patches living in the mailing list waiting for someone to merge them. I
> hope I'm wrong on that and that such fixes will be committed soon :)

I hope so.  :)

> 
> >
> >> 
> >> [...]
> >> 
> >> > +#ifdef CONFIG_UTIMENSAT
> >> > +
> >> > +#ifdef TARGET_NR_utimensat
> >> > +static int sys_utimensat(int dirfd, const char *pathname,
> >> > +    const struct timespec times[2], int flags)
> >> > +{
> >> > +  return (utimensat(dirfd, pathname, times, flags));
> >> > +}
> >> 
> >> As you'll see when reading the thread I mentionned, this is broken.
> >
> > I don't see why it is broken, unless current qemu code is broken
> > too. I
> 
> current qemu code is broken too.

Now this makes sense.

> 
> > just changed it to use the !CONFIG_ATFILE sys_utimensat() implementation
> > (that was already present on the code) if glibc doesn't provide
> > utimensat(). What do you suggest instead?
> 
> glibc utimensat is not exactly the syscall, a test on some parameters
> has been added. There's code to handle this in the patch I was talking
> about.

Understood. However, my patch addresses a different issue, that is the
case where the host system doesn't have utimensat() available. The point
here is to disable the code that uses utimensat() (be it broken or not)
on that case.

And the first patch is unrelated to that question: it is just a
correctness issue to make sure the xxxat() availability matches the
situation detected by ./configure (whose test code has #define
_ATFILE_SOURCE).
-- 
Eduardo

  reply	other threads:[~2009-06-10 19:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:26 [Qemu-devel] [PATCH 0/2] linux-user: fix build error against older glibcs Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 1/2] linux-user/syscall.c: define _ATFILE_SOURCE Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure Eduardo Habkost
2009-06-09 22:06   ` Arnaud Patard
2009-06-10 14:12     ` Eduardo Habkost
2009-06-10 14:39       ` Arnaud Patard
2009-06-10 19:10         ` Eduardo Habkost [this message]
2009-06-10 21:48           ` Riku Voipio
2009-06-10 22:09             ` Eduardo Habkost
2009-06-11 15:14               ` Riku Voipio
2009-06-10 16:07       ` Riku Voipio
2009-06-10 16:20         ` Glauber Costa
2009-06-10 16:30           ` Arnaud Patard
2009-06-10 16:56             ` Glauber Costa
2009-06-10 22:05               ` Riku Voipio
2009-06-11  8:33                 ` Arnaud Patard
2009-06-11 15:09                   ` Riku Voipio
2009-06-12  8:30                     ` ltp vs linux-user (was: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure) Arnaud Patard
2009-06-11 11:27                 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure vibi sreenivasan
2009-06-12 13:24                 ` vibi sreenivasan
2009-06-10 15:03     ` Glauber Costa
2009-06-10 21:53       ` 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=1244659259-sup-8660@blackpad \
    --to=ehabkost@raisama.net \
    --cc=arnaud.patard@rtp-net.org \
    --cc=glommer@redhat.com \
    --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).