From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753781AbcIDLfm convert rfc822-to-8bit (ORCPT ); Sun, 4 Sep 2016 07:35:42 -0400 Received: from mga02.intel.com ([134.134.136.20]:6381 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752181AbcIDLfi (ORCPT ); Sun, 4 Sep 2016 07:35:38 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,280,1470726000"; d="scan'208";a="1024926113" From: "Winkler, Tomas" To: Greg Kroah-Hartman CC: Pavel Machek , Ulf Hansson , "Hunter, Adrian" , James Bottomley , "Martin K. Petersen" , Vinayak Holikatti , Andy Lutomirski , Arve Hj?nnev?g , "Michael Ryleev" , Joao Pinto , "Christoph Hellwig" , Yaniv Gardi , "linux-kernel@vger.kernel.org" , "linux-mmc@vger.kernel.org" , "linux-scsi@vger.kernel.org" Subject: RE: [PATCH v5 4/8] char: rpmb: provide a user space interface Thread-Topic: [PATCH v5 4/8] char: rpmb: provide a user space interface Thread-Index: AQHR71UzA6wBb7OMAk2Dd+NUuhN0zKA9P4sAgCWaUYCAAlyh4P//3GaAgARLdzA= Date: Sun, 4 Sep 2016 11:35:33 +0000 Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B542C6CC0@hasmsx108.ger.corp.intel.com> References: <1468873673-21776-1-git-send-email-tomas.winkler@intel.com> <1468873673-21776-5-git-send-email-tomas.winkler@intel.com> <20160805200823.GB7999@amd> <5B8DA87D05A7694D9FA63FD143655C1B542B8AC9@hasmsx108.ger.corp.intel.com> <20160831104955.GA10180@kroah.com> <5B8DA87D05A7694D9FA63FD143655C1B542C5B6F@hasmsx108.ger.corp.intel.com> <20160901204633.GB5960@kroah.com> In-Reply-To: <20160901204633.GB5960@kroah.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODgyMTBhY2EtODFhMi00NzkxLThmZjAtMmM3MjYwZGMyNjQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlJlVThmZk1yU09sRlh6MHhwVW1waGZIbDhOZVFrY1k3b1lodCtaXC9HQnVnPSJ9 x-originating-ip: [10.184.70.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Thu, Sep 01, 2016 at 08:05:26PM +0000, Winkler, Tomas wrote: > > > > > > > > On Sun, Aug 07, 2016 at 09:44:03AM +0000, Winkler, Tomas wrote: > > > > > > > > > > On Mon 2016-07-18 23:27:49, Tomas Winkler wrote: > > > > > > The user space API is achieved via two synchronous IOCTL. > > > > > > > > > > IOCTLs? > > > > > > > > Will fix > > > > > > > > > > Simplified one, RPMB_IOC_REQ_CMD, were read result cycles is > > > > > performed > > > > > > by the framework on behalf the user and second, > > > > > > RPMB_IOC_SEQ_CMD > > > > > where > > > > > > the whole RPMB sequence including RESULT_READ is supplied by > > > > > > the > > > caller. > > > > > > The latter is intended for easier adjusting of the > > > > > > applications that use MMC_IOC_MULTI_CMD ioctl. > > > > > > > > > > Why " "? > > > > Not sure I there is enough clue in your question. > > > > > > > > > > > > > > > > > Signed-off-by: Tomas Winkler > > > > > > > > > > > + > > > > > > +static long rpmb_ioctl(struct file *fp, unsigned int cmd, > > > > > > +unsigned long arg) { > > > > > > + return __rpmb_ioctl(fp, cmd, (void __user *)arg); } > > > > > > + > > > > > > +#ifdef CONFIG_COMPAT > > > > > > +static long rpmb_compat_ioctl(struct file *fp, unsigned int cmd, > > > > > > + unsigned long arg) > > > > > > +{ > > > > > > + return __rpmb_ioctl(fp, cmd, compat_ptr(arg)); > > > > > > +} > > > > > > +#endif /* CONFIG_COMPAT */ > > > > > > > > > > Description of the ioctl is missing, > > > > Will add. > > > > > > > > and it should certainly be designed in a way > > > > > that it does not need compat support. > > > > > > > > The compat_ioctl handler just casts the compat_ptr, I believe this > > > > should be done unless the ioctl is globaly registered in > > > > fs/compat_ioctl.c, but I might be wrong. > > > > > > You shouldn't need a compat ioctl for anything new that is added, > > > unless your api is really messed up. Please test to be sure, and > > > not use a compat ioctl at all, it isn't that hard to do. > > > > compat_ioctl is called anyhow when CONFIG_COMPAT is set, there is no > > way around it, or I'm missing something? Actually there is no more > > than that for the COMPAT support in this code. > > If you don't provide a compat_ioctl() all should be fine, right? No, this doesn't work the driver has to provide compat_ioctl You would expect something like if (!f.file->f_op->compat_ioctl) { error = f_op->f.file->f_op->unlocked_ioctl((f.file, cmd, compat_ptr(arg)) } But there is no such code under fs/compat_ioctl.c The translation has to implemented by the device driver or registered directly in fs/compat_ioct.c in do_ioctl_trans or ioctl_pointer[] If compat_ioct is not provided the application is receiving : ioctl failure -1: Inappropriate ioctl for device Thanks Tomas