linux-kernel - Re: [PATCH] drm: convert drm_ioctl to unlocked

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: <200912180916.27201.arnd@arndb.de>
Date:	Fri, 18 Dec 2009 09:16:27 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Dave Airlie <airlied@...il.com>
Cc:	David Airlie <airlied@...ux.ie>, dri-devel@...ts.sourceforge.net,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm: convert drm_ioctl to unlocked_ioctl

On Friday 18 December 2009, Dave Airlie wrote:
> This looks good, I've taken this and I've squashed
> the generic pieces of your RFC into this (i.e.
> I haven't modified the drivers, but just added the
> flag to allow the ioctls to be unlocked if the driver
> selects them).
> 
> Do you think we should try and get this in soon,
> its seems like it shouldn't have any regressions
> unless we start switching drivers over.

Well, since the patch should not change the behaviour
of the drivers, it probably doesn't matter to users
either way. However, it touches a number of places,
which can break patches that others are working on,
so maybe you should get it upstream at a point that
has the least impact to developer (possibly now).

Doing it now at least makes it easier to test
moving drivers to unlocked operation.

	Arnd
--
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/