From: Cornelia Huck <cohuck@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Riku Voipio" <riku.voipio@iki.fi>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] linux-user: emulate msgsnd(), msgrcv() and semtimedop()
Date: Wed, 29 May 2019 11:31:19 +0200 [thread overview]
Message-ID: <20190529113119.58212175.cohuck@redhat.com> (raw)
In-Reply-To: <20190529084804.25950-1-laurent@vivier.eu>
On Wed, 29 May 2019 10:48:04 +0200
Laurent Vivier <laurent@vivier.eu> wrote:
> When we have updated kernel headers to 5.2-rc1 we have introduced
> new syscall numbers that can be not supported by older kernels
> and fail with ENOSYS while the guest emulation succeeded before
> because the syscalls were emulated with ipc().
>
> This patch fixes the problem by using ipc() if the new syscall
> returns ENOSYS.
>
> Fixes: 86e636951ddc ("linux-user: fix __NR_semtimedop undeclared error")
> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
> ---
>
> Notes:
> v2: replace ENOSYS by TARGET_ENOSYS
>
> linux-user/syscall.c | 61 +++++++++++++++++++--------------------
> linux-user/syscall_defs.h | 1 +
> 2 files changed, 31 insertions(+), 31 deletions(-)
I hope this headers update is now done with bringing joy :)
Not a linux-user expert, but it does look reasonable.
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-05-29 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 8:48 [Qemu-devel] [PATCH v2] linux-user: emulate msgsnd(), msgrcv() and semtimedop() Laurent Vivier
2019-05-29 9:31 ` Cornelia Huck [this message]
2019-06-24 21:00 ` Laurent Vivier
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=20190529113119.58212175.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).