From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: Patch: Sparc prevent segfault when dumping uninitialzed cpu state
Date: Sun, 2 Feb 2025 19:45:59 -0800 [thread overview]
Message-ID: <abbdad0c-fc98-4ec4-b69a-8d91dbd49554@linaro.org> (raw)
In-Reply-To: <eb7fe8ed-e885-48c0-a36f-1f700bc692bf@laaksoft.nl>
On 2/2/25 19:14, Henk van der Laak (LaakSoft) via wrote:
> Hi all, my first contribution. I checked code style, patch submission rules and did a
> manual test (details on request)
>
> Synopsis:
> It's a corner case, where a segfault occurs when logging Sparc CPU state in a partially
> initialized state.
>
> No related bug report.
>
> Open to harsh criticism ;-)
How do we arrive here with a partially initialized state?
r~
next prev parent reply other threads:[~2025-02-03 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 3:14 Patch: Sparc prevent segfault when dumping uninitialzed cpu state Henk van der Laak (LaakSoft) via
2025-02-03 3:45 ` Richard Henderson [this message]
[not found] ` <a392d217-852c-46b4-84ef-d8ea5ad296c1@laaksoft.nl>
2025-02-03 4:10 ` Richard Henderson
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=abbdad0c-fc98-4ec4-b69a-8d91dbd49554@linaro.org \
--to=richard.henderson@linaro.org \
--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).