From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/arm/arm-semi: Don't let the guest close stdin/stdout/stderr
Date: Mon, 27 Jan 2020 08:49:19 +0100 [thread overview]
Message-ID: <44ee8563-ced3-9416-4e79-1dccba02d27b@redhat.com> (raw)
In-Reply-To: <87zhec8w67.fsf@linaro.org>
On 1/24/20 8:57 PM, Alex Bennée wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> The guest can use the semihosting API to open a handle
>> corresponding to QEMU's own stdin, stdout, or stderr.
>> When the guest closes this handle, we should not
>> close the underlying host stdin/stdout/stderr
>> the way we would do if the handle corresponded to
>> a host fd we'd opened on behalf of the guest in SYS_OPEN.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> target/arm/arm-semi.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/target/arm/arm-semi.c b/target/arm/arm-semi.c
>> index 788fe61b51a..8718fd01948 100644
>> --- a/target/arm/arm-semi.c
>> +++ b/target/arm/arm-semi.c
>> @@ -403,6 +403,15 @@ static uint32_t host_closefn(ARMCPU *cpu, GuestFD *gf)
>> {
>> CPUARMState *env = &cpu->env;
>>
>> + /*
>> + * Only close the underlying host fd if it's one we opened on behalf
>> + * of the guest in SYS_OPEN.
>> + */
>> + if (gf->hostfd == STDIN_FILENO ||
>> + gf->hostfd == STDOUT_FILENO ||
>> + gf->hostfd == STDERR_FILENO) {
>> + return 0;
>> + }
>> return set_swi_errno(env, close(gf->hostfd));
>> }
prev parent reply other threads:[~2020-01-27 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 17:29 [PATCH] target/arm/arm-semi: Don't let the guest close stdin/stdout/stderr Peter Maydell
2020-01-24 19:57 ` Alex Bennée
2020-01-27 7:49 ` Philippe Mathieu-Daudé [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=44ee8563-ced3-9416-4e79-1dccba02d27b@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).