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]

Date:	Wed, 28 Oct 2009 05:17:03 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	arndbergmann@...glemail.com
Cc:	airlied@...ux.ie, dri-devel@...ts.sourceforge.net,
	andi@...stfloor.org, linux-kernel@...r.kernel.org
Subject: Re: is avoiding compat ioctls possible?

From: Arnd Bergmann <arndbergmann@...glemail.com>
Date: Wed, 28 Oct 2009 13:13:32 +0100

> IMHO a better way to handle the radeon specific ioctls would be to
> avoid the compat_alloc_user_space and just define the common
> function taking a kernel pointer, with two implementations of the
> copy operation:

Agreed, that would be a great follow-on patch to mine.
--
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/