qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Thomas Huth <thuth@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	 QEMU Developers <qemu-devel@nongnu.org>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: any remaining for-6.0 issues?
Date: Wed, 14 Apr 2021 15:15:04 +0100	[thread overview]
Message-ID: <7760731b-ae34-89aa-a5de-65828ec9ae79@ilande.co.uk> (raw)
In-Reply-To: <c63bbf7e-2230-44b2-7671-086c7dacd787@ilande.co.uk>

On 14/04/2021 14:57, Mark Cave-Ayland wrote:

> I've definitely seen the same issue as Cornelia in my Gitlab CI builds for the ESP 
> security fixes (first version of which appeared just before rc0). The user builds 
> always fail on "run-tcg-tests-s390x-linux-user" for me.

Commit 23fff7a17f lies within that range and certainly feels like it could be 
relevant to the above failure:


commit 23fff7a17f47420797ac6480147941612152a9ad
Author: Andreas Krebbel <krebbel@linux.ibm.com>
Date:   Wed Mar 24 19:51:28 2021 +0100

     linux-user/s390x: Use the guest pointer for the sigreturn stub

     When setting up the pointer for the sigreturn stub in the return
     address register (r14) we currently use the host frame address instead
     of the guest frame address.

     Note: This only caused problems if Qemu has been built with
     --disable-pie (as it is in distros nowadays). Otherwise guest_base
     defaults to 0 hiding the actual problem.

     Signed-off-by: Andreas Krebbel <krebbel@linux.ibm.com>
     Reviewed-by: Laurent Vivier <laurent@vivier.eu>
     Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
     Message-Id: <20210324185128.63971-1-krebbel@linux.ibm.com>
     Signed-off-by: Laurent Vivier <laurent@vivier.eu>


I'll try pushing a test build to Gitlab CI with a revert for that patch on top and 
see if it succeeds for me...


ATB,

Mark.


  reply	other threads:[~2021-04-14 14:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 15:32 any remaining for-6.0 issues? Peter Maydell
2021-04-12 18:44 ` Mark Cave-Ayland
2021-04-12 19:40   ` Peter Maydell
2021-04-12 21:13     ` Mark Cave-Ayland
2021-04-12 22:19     ` Mark Cave-Ayland
2021-04-13  4:38 ` Markus Armbruster
2021-04-13  5:56 ` Bin Meng
2021-04-13  6:19   ` Stefan Weil
2021-04-14  8:30     ` Bin Meng
2021-04-14  9:18       ` Stefan Weil
2021-04-14  9:34       ` Peter Maydell
2021-04-14 12:57         ` Bin Meng
2021-04-14 12:48 ` Thomas Huth
2021-04-14 13:57   ` Mark Cave-Ayland
2021-04-14 14:15     ` Mark Cave-Ayland [this message]
2021-04-14 14:36       ` Cornelia Huck
2021-04-14 16:26         ` Mark Cave-Ayland
2021-04-17 19:46     ` Peter Maydell
2021-04-18 10:38       ` Mark Cave-Ayland
2021-04-19  7:05         ` Cornelia Huck
2021-04-19 17:02           ` Cornelia Huck
2021-04-19 19:38             ` Mark Cave-Ayland
2021-04-20  9:58               ` Cornelia Huck

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=7760731b-ae34-89aa-a5de-65828ec9ae79@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /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).