From: Arnd Bergmann <arnd@arndb.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 5/7] FUSE: implement ioctl support
Date: Fri, 29 Aug 2008 21:47:26 +0200
User-Agent: KMail/1.9.9
Cc: Tejun Heo <tj@kernel.org>, Miklos Szeredi <miklos@szeredi.hu>,
       Serge Hallyn <serue@us.ibm.com>, greg@kroah.com,
       fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
References: <1219945263-21074-1-git-send-email-tj@kernel.org> <48B7BB4C.4060907@kernel.org> <m163pjr5qf.fsf@frodo.ebiederm.org>
In-Reply-To: <m163pjr5qf.fsf@frodo.ebiederm.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200808292147.27720.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 865
Lines: 21

On Friday 29 August 2008, Eric W. Biederman wrote:
> However it is a largely an insane idea.

I fully agree.

> Given the pain it is to maintain ioctls I would be very surprised if we wanted
> to open up that pandoras box even wider by allowing arbitrary user space
> processes to support random ioctls. ?How would you do 32/64bit support
> and the like?

I think that is not too much of a problem: Just like the file operations in
the kernel have two callbacks (ioctl and compat_ioctl), you need to provide
both operations from user space if there is a difference between them, or
at least a stub otherwise.

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