qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Giuseppe Musacchio <thatlemon@gmail.com>, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH] Avoid crash in epoll_ctl with EPOLL_CTL_DEL
Date: Thu, 30 May 2019 18:12:06 +0200	[thread overview]
Message-ID: <f1184a82-29e4-ba41-2f44-dd4b3e0f15a9@vivier.eu> (raw)
In-Reply-To: <64eb15b1-ed5c-d12e-5f56-8a2b40df8041@vivier.eu>

Le 30/05/2019 à 18:00, Laurent Vivier a écrit :
> Le 30/05/2019 à 17:25, Giuseppe Musacchio a écrit :
>> The `event` parameter is ignored by the kernel if `op` is EPOLL_CTL_DEL,
>> do the same and avoid returning EFAULT if garbage is passed instead of a
>> valid pointer.
>>
>> Signed-off-by: Giuseppe Musacchio <thatlemon@gmail.com>
>> ---
>>  linux-user/syscall.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>> index 5e29e675e9..32d463d58d 100644
>> --- a/linux-user/syscall.c
>> +++ b/linux-user/syscall.c
>> @@ -11329,7 +11329,7 @@ static abi_long do_syscall1(void *cpu_env, int
>> num, abi_long arg1,
>>      {
>>          struct epoll_event ep;
>>          struct epoll_event *epp = 0;
>> -        if (arg4) {
>> +        if (arg2 != EPOLL_CTL_DEL && arg4) {
>>              struct target_epoll_event *target_ep;
>>              if (!lock_user_struct(VERIFY_READ, target_ep, arg4, 1)) {
>>                  return -TARGET_EFAULT;
> 
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> 

in fact, the BUGS section of epoll_ctl(2) says:

"In kernel versions before 2.6.9, the EPOLL_CTL_DEL operation required a
 non-null pointer in event, even though this argument is ignored.  Since
 Linux 2.6.9, event can be specified as NULL when  using  EPOLL_CTL_DEL.
 Applications  that  need  to be portable to kernels before 2.6.9 should
 specify a non-null pointer in event."

So something like this would be more portable:

@@ -11329,6 +11329,7 @@ static abi_long do_syscall1(void *cpu_env, int
num, abi_long arg1,
         struct epoll_event ep;
         struct epoll_event *epp = 0;
         if (arg4) {
+            if (arg2 != EPOLL_CTL_DEL) {
                 struct target_epoll_event *target_ep;
                 if (!lock_user_struct(VERIFY_READ, target_ep, arg4, 1)) {
                     return -TARGET_EFAULT;
@@ -11340,6 +11341,11 @@ static abi_long do_syscall1(void *cpu_env, int
num, abi_long arg1,
                  */
                 ep.data.u64 = tswap64(target_ep->data.u64);
                 unlock_user_struct(target_ep, arg4, 0);
+            }
+            /*
+             * before kernel 2.6.9, EPOLL_CTL_DEL operation required a
+             * non-null pointer, even though this argument is ignored.
+             * */
             epp = &ep;
         }

Thanks,
Laurent


  reply	other threads:[~2019-05-30 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 15:25 [Qemu-devel] [PATCH] Avoid crash in epoll_ctl with EPOLL_CTL_DEL Giuseppe Musacchio
2019-05-30 16:00 ` Laurent Vivier
2019-05-30 16:12   ` Laurent Vivier [this message]
2019-05-30 19:48     ` Giuseppe Musacchio

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=f1184a82-29e4-ba41-2f44-dd4b3e0f15a9@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=thatlemon@gmail.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).