Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753564AbZJ1MQJ (ORCPT ); Wed, 28 Oct 2009 08:16:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753514AbZJ1MQI (ORCPT ); Wed, 28 Oct 2009 08:16:08 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:35938 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753455AbZJ1MQI (ORCPT ); Wed, 28 Oct 2009 08:16:08 -0400 Date: Wed, 28 Oct 2009 05:16:31 -0700 (PDT) Message-Id: <20091028.051631.212225494.davem@davemloft.net> To: arndbergmann@googlemail.com Cc: airlied@linux.ie, dri-devel@lists.sourceforge.net, andi@firstfloor.org, linux-kernel@vger.kernel.org Subject: Re: is avoiding compat ioctls possible? From: David Miller In-Reply-To: <200910281313.32827.arnd@arndb.de> References: <20091027.230450.222178419.davem@davemloft.net> <20091028.005342.60092591.davem@davemloft.net> <200910281313.32827.arnd@arndb.de> X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 20 From: Arnd Bergmann Date: Wed, 28 Oct 2009 13:13:32 +0100 > The ioctl argument actually needs a compat_ptr() conversion as well. > For the s390 case, we can't do that in common code, because some > ioctl methods put a 32 bit integer into the argument. Not sure if we > want to fix that everywhere, the problem is very common and the > impact is minimal. What does s390 do with the 'arg' argument to sys_ioctl()? That assumption that you can cast this to a pointer is everywhere. If someone wants to fix this up, feel free to do an audit and go over that seperately from my work :-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/