All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sodagudi Prasad <psodagud@codeaurora.org>
To: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org
Subject: opaque types instead of union epoll_data
Date: Tue, 07 Mar 2017 04:31:19 -0800	[thread overview]
Message-ID: <c06a9ceff1f2c8919ca81120de69f172@codeaurora.org> (raw)

Hi All,

uapi structs epoll_data are more opaque than user space expects. kernel 
have defined as __u64 instead of the union epoll_data.
Because of this libc have redefined struct epoll_event with union data 
member.

https://android.googlesource.com/platform/bionic.git/+/master/libc/include/sys/epoll.h
typedef union epoll_data {
   void* ptr;
   int fd;
   uint32_t u32;
   uint64_t u64;
} epoll_data_t;
struct epoll_event {
   uint32_t events;
   epoll_data_t data;
}

Kernel UAPI header defined as "include/uapi/linux/eventpoll.h"
struct epoll_event {
         __u32 events;
         __u64 data;  =====>opaque type instead of union epoll_data
} EPOLL_PACKED;


Because of this we are landing into some issues as we copy kernel 
headers. Will it be going to be addressed?

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
Linux Foundation Collaborative Project

             reply	other threads:[~2017-03-07 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 12:31 Sodagudi Prasad [this message]
     [not found] ` <c06a9ceff1f2c8919ca81120de69f172-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-03-07 14:33   ` opaque types instead of union epoll_data Carlos O'Donell
2017-03-07 14:33     ` Carlos O'Donell
2017-03-07 17:59     ` Greg KH
     [not found]       ` <20170307175931.GA31000-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-03-08 17:34         ` Carlos O'Donell
2017-03-08 17:34           ` Carlos O'Donell
     [not found]           ` <ba7d0715-b59a-6596-9ec0-435999cd0e76-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-08 18:01             ` Greg KH
2017-03-08 18:01               ` Greg KH

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=c06a9ceff1f2c8919ca81120de69f172@codeaurora.org \
    --to=psodagud@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.