[PATCH 4/5] Update linux/ioctlent.h.in file

[Gabriel Laskar]

On Thu, Jan 15, 2015 at 9:03 PM, enh <enh at google.com> wrote:
> is there anything we can do about the SND* mess? the most common
> conflict i see on Android is the same one i see on my desktop:
>
> ioctl(1, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or
> TCGETS, {B38400 opost isig icanon echo ...}) = 0
>
> Android does use _some_ of the SND* ioctls, so i don't want to just
> hack them all out of our strace.

I am already looking into this kind of cases, but I don't know if this
kind of patches would be accepted.

There is a way to avoid the conflict, but it seems a bit much.

I can stat() the path associated to the fd, get the major/minor
number, and, if I store the major number associated to the ioctls in
ioctlent table, I can find the right one. It will require to hack a
little into ioctlent.sh in order to add the major numbers, increase
the binary size, but it will solve almost all the conflicts.

On DRM, it will not solve the conflicts for the device specific
ioctls, but it should be feasible.

-- 
Gabriel Laskar