From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: cohuck@redhat.com
Subject: Re: [PATCH 0/5] target/s390x: Do not leak stack address in translate_one
Date: Fri, 24 Jan 2020 10:43:32 +0100 [thread overview]
Message-ID: <41ea3b7b-745d-4d8a-24fa-3862035db41d@redhat.com> (raw)
In-Reply-To: <20200123232248.1800-1-richard.henderson@linaro.org>
On 24/01/2020 00.22, Richard Henderson wrote:
> Thomas' patch avoids the leak, but I think we can do a bit more to
> cleaning in this area, and move the structure inline to DisasContext.
>
Sounds like a good idea to me. Cornelia, could you please replace my
patch with Richard's series?
Thanks,
Thomas
next prev parent reply other threads:[~2020-01-24 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 23:22 [PATCH 0/5] target/s390x: Do not leak stack address in translate_one Richard Henderson
2020-01-23 23:22 ` [PATCH 1/5] target/s390x: Move struct DisasFields definition earlier Richard Henderson
2020-01-24 8:44 ` Thomas Huth
2020-01-23 23:22 ` [PATCH 2/5] target/s390x: Remove DisasFields argument from callbacks Richard Henderson
2020-01-24 9:21 ` Thomas Huth
2020-01-23 23:22 ` [PATCH 3/5] target/s390x: Pass DisasContext to get_field and have_field Richard Henderson
2020-01-24 9:37 ` Thomas Huth
2020-01-23 23:22 ` [PATCH 4/5] target/s390x: Move DisasFields into DisasContext Richard Henderson
2020-01-24 9:39 ` Thomas Huth
2020-01-23 23:22 ` [PATCH 5/5] target/s390x: Remove DisasFields argument from extract_insn Richard Henderson
2020-01-24 9:42 ` Thomas Huth
2020-01-24 9:43 ` Thomas Huth [this message]
2020-01-24 14:25 ` [PATCH 0/5] target/s390x: Do not leak stack address in translate_one Cornelia Huck
2020-01-24 14:25 ` 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=41ea3b7b-745d-4d8a-24fa-3862035db41d@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).