From: "J. Mayer" <l_indien@magic.fr>
To: thayne@c2.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] syscall_target_errno.patch
Date: Thu, 11 Oct 2007 14:10:33 +0200 [thread overview]
Message-ID: <1192104633.9976.216.camel@rapid> (raw)
In-Reply-To: <1192073888.8097.14.camel@phantasm.home.enterpriseandprosperity.com>
On Wed, 2007-10-10 at 21:38 -0600, Thayne Harbaugh wrote:
> I appreciate the work that Jocelyn did to correct the types used
> throughout linux-user/syscall.c. Along those same lines I am working on
> several patches to eliminate some incorrect constructs that have crept
> into syscall.c - some of which I have ignorantly propagated in previous
> patches that I have submitted.
>
> I have noticed that many functions in syscall.c return a *host* errno
> when a *target* errno should be return. At the same time, there are
> several places in syscall.c:do_syscall() that immediately return an
> errno rather than setting the return value and exiting through the
> syscall return value reporting at the end of do_syscall().
>
> This patch addresses both of those problems at once rather than touching
> the exact same errno return lines twice in do_syscall(). It also
> touches a few functions in linux-user/signal.c that are called from
> do_syscall().
>
> Please send comments - I have several more patches that will build on
> this one as well as a few more patches that will fix other incorrect
> constructs with target/host address handling.
>
> Thanks.
Hi,
there are still a lot of problems hidden in syscalls.c and signal.c, as
you noticed.
Your patch seems OK to me and adding all those comments is imho really
great.
My only remark is a cosmetic one: I don't like too much hidding 'goto'
in macros...
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-11 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 3:38 [Qemu-devel] [PATCH] syscall_target_errno.patch Thayne Harbaugh
2007-10-11 12:10 ` J. Mayer [this message]
2007-10-15 18:01 ` Thayne Harbaugh
2007-10-12 15:00 ` Thayne Harbaugh
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=1192104633.9976.216.camel@rapid \
--to=l_indien@magic.fr \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.net \
/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).