From: "Andreas Färber" <afaerber@suse.de>
To: Alex Barcelo <abarcelo@ac.upc.edu>
Cc: qemu-trivial@nongnu.org, Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [TRIVIAL] sas_ss_flags bug for powerpc
Date: Thu, 09 Feb 2012 19:43:37 +0100 [thread overview]
Message-ID: <4F3413D9.7040204@suse.de> (raw)
In-Reply-To: <CAFKAgTdwXj_XZ3EOgwR0=x_biz6s=SJKVsKX5C+z38=SicWY2A@mail.gmail.com>
Am 09.02.2012 19:30, schrieb Alex Barcelo:
> Signed-off-by: Alex Barcelo <abarcelo@ac.upc.edu>
This patch needs a better description than "bug", and you forgot to cc
the linux-user maintainer. The patch should describe what it touches
(linux-user), what it does, what for and make clear why that is correct.
Is there a particular test case that's broken without the patch?
I can't speak for Stefan, but to me it is totally unclear from looking
at the patch what sas_ss_flags() does here so this is likely not really
a trivial one.
Andreas
> ---
> linux-user/signal.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/linux-user/signal.c b/linux-user/signal.c
> index 79a39dc..26e0530 100644
> --- a/linux-user/signal.c
> +++ b/linux-user/signal.c
> @@ -4115,7 +4115,7 @@ static target_ulong get_sigframe(struct
> target_sigaction *ka,
> oldsp = env->gpr[1];
>
> if ((ka->sa_flags & TARGET_SA_ONSTACK) &&
> - (sas_ss_flags(oldsp))) {
> + (sas_ss_flags(oldsp)) == 0) {
> oldsp = (target_sigaltstack_used.ss_sp
> + target_sigaltstack_used.ss_size);
> }
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-02-09 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:30 [Qemu-devel] [TRIVIAL] sas_ss_flags bug for powerpc Alex Barcelo
2012-02-09 18:43 ` Andreas Färber [this message]
2012-02-09 19:00 ` Alex Barcelo
2012-02-10 8:23 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-02-10 12:52 ` Paul Brook
2012-02-10 13:27 ` Alex Barcelo
2012-02-09 22:52 ` [Qemu-devel] " Alexander Graf
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=4F3413D9.7040204@suse.de \
--to=afaerber@suse.de \
--cc=abarcelo@ac.upc.edu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).