From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org
Cc: kirill@shutemov.name
Subject: Re: [Qemu-devel] [PATCH] add futimesat syscall
Date: Thu, 18 Sep 2008 12:08:21 +0300 [thread overview]
Message-ID: <20080918090821.GA17893@kos.to> (raw)
In-Reply-To: <761ea48b0809180023t37d300ceq790fe33c5ab7602a@mail.gmail.com>
On Thu, Sep 18, 2008 at 09:23:20AM +0200, Laurent Desnogues wrote:
> On Thu, Sep 18, 2008 at 8:30 AM, Riku Voipio <riku.voipio@iki.fi> wrote:
> > On Thu, Sep 18, 2008 at 01:54:21AM +0200, andrzej zaborowski wrote:
> >> http://lists.gnu.org/archive/html/qemu-devel/2008-09/msg00439.html ,
> >> it looks cleaner to me.
> > Kirill's patch looks good to me.
> There's a functional difference between Kirill's patch and yours:
> Kirill + ret = get_errno(futimesat(arg1, p, tvp));
> you + ret = get_errno(sys_futimesat(arg1, path(p), tv));
The sbox patch defines sys_futimesat earlier in the file, presumably to
deal with supporting a stone-age version of libc/kernel headers.
path() is related to interp_prefix. The old utimes handlers don't use
path() either, and it's unlikely that any library-loading routine uses
futimes(). Thus, I believe Kirill's version is more correct.
That said, path() should probably renamed to something more obvious
(interp_path() ?), or path mangling could be made more generic (allowing
things like chroot() emulation).
--
"rm -rf" only sounds scary if you don't have backups
next prev parent reply other threads:[~2008-09-18 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 19:45 [Qemu-devel] [PATCH] add futimesat syscall Riku Voipio
2008-09-17 23:54 ` andrzej zaborowski
2008-09-18 5:00 ` Kirill A. Shutemov
2008-09-18 6:30 ` Riku Voipio
2008-09-18 7:23 ` Laurent Desnogues
2008-09-18 9:08 ` Riku Voipio [this message]
2008-09-18 9:28 ` Kirill A. Shutemov
2008-09-18 9:42 ` Riku Voipio
2008-09-18 10:16 ` Kirill A. Shutemov
2008-09-18 11:13 ` Thiemo Seufer
2008-09-18 11:45 ` Kirill A. Shutemov
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=20080918090821.GA17893@kos.to \
--to=riku.voipio@iki.fi \
--cc=kirill@shutemov.name \
--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).