From: Richard Henderson <richard.henderson@linaro.org>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v4 0/4] Fix deadlock when dying because of a signal
Date: Wed, 15 Feb 2023 20:09:45 -1000 [thread overview]
Message-ID: <4d2046c4-85c8-a73a-017b-3c3829221573@linaro.org> (raw)
In-Reply-To: <20230214140829.45392-1-iii@linux.ibm.com>
On 2/14/23 04:08, Ilya Leoshkevich wrote:
> Based-on:<20230202005204.2055899-1-richard.henderson@linaro.org>
> ("[PATCH 00/14] linux-user/sparc: Handle missing traps")
>
> v3:https://lists.gnu.org/archive/html/qemu-devel/2023-02/msg03534.html
> v3 -> v4: Add printfs to the test in order to make the uncaught signals
> less scary:
>
> $ build/x86_64-linux-user/qemu-x86_64 build/tests/tcg/x86_64-linux-user/linux-fork-trap
> about to trigger fault...
> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
> faulting thread exited cleanly
Queued to tcg-next, thanks.
r~
prev parent reply other threads:[~2023-02-16 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:08 [PATCH v4 0/4] Fix deadlock when dying because of a signal Ilya Leoshkevich
2023-02-14 14:08 ` [PATCH v4 1/4] linux-user: Always exit from exclusive state in fork_end() Ilya Leoshkevich
2023-02-14 14:08 ` [PATCH v4 2/4] cpus: Make {start,end}_exclusive() recursive Ilya Leoshkevich
2023-02-14 14:08 ` [PATCH v4 3/4] linux-user/microblaze: Handle privileged exception Ilya Leoshkevich
2023-02-14 14:08 ` [PATCH v4 4/4] tests/tcg/linux-test: Add linux-fork-trap test Ilya Leoshkevich
2023-02-16 6:09 ` Richard Henderson [this message]
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=4d2046c4-85c8-a73a-017b-3c3829221573@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@linux.ibm.com \
--cc=eduardo@habkost.net \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.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).