linux-kernel - Re: is avoiding compat ioctls possible?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21d7e9970910272001y77682572od540572bdac4eb54@mail.gmail.com>
Date:	Wed, 28 Oct 2009 13:01:36 +1000
From:	Dave Airlie <airlied@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org, dri-devel@...ts.sourceforge.net,
	arnd@...db.de
Subject: Re: is avoiding compat ioctls possible?

On Wed, Oct 28, 2009 at 12:25 PM, David Miller <davem@...emloft.net> wrote:
> From: Dave Airlie <airlied@...il.com>
> Date: Wed, 28 Oct 2009 11:22:18 +1000
>
>> Is there really no way to avoid compat ioctls? was I delusional in
>> thinking there was?
>
> If you use pointers in your interfaces in any way, no.
>
> And for this drm_radeon_info thing the pointer is "pointless",
> you're just returning 32-bit values to the user, just use
> a u32 inside of the drm_radeon_info structure for the kernel
> to place the result in.

The plan for that was to expand it later, for now 32-bit was all we used.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/