From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753014AbeE3Lav (ORCPT ); Wed, 30 May 2018 07:30:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:45746 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbeE3Lar (ORCPT ); Wed, 30 May 2018 07:30:47 -0400 Date: Wed, 30 May 2018 13:30:26 +0200 From: Greg Kroah-Hartman To: Marcus Folkesson Cc: Andy Shevchenko , Jonathan Corbet , Felipe Balbi , "David S. Miller" , Mauro Carvalho Chehab , Andrew Morton , Randy Dunlap , Ruslan Bilovol , Thomas Gleixner , Kate Stewart , USB , Linux Documentation List , Linux Kernel Mailing List Subject: Re: [PATCH v3 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device Message-ID: <20180530113026.GA20775@kroah.com> References: <20180529185021.13738-1-marcus.folkesson@gmail.com> <20180530112459.GB2939@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180530112459.GB2939@gmail.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 30, 2018 at 01:24:59PM +0200, Marcus Folkesson wrote: > Hi Andy, > > Thank you for your comments! > Many good catches here! > > On Wed, May 30, 2018 at 03:55:39AM +0300, Andy Shevchenko wrote: > > On Tue, May 29, 2018 at 9:50 PM, Marcus Folkesson > > wrote: > > > Chip Card Interface Device (CCID) protocol is a USB protocol that > > > allows a smartcard device to be connected to a computer via a card > > > reader using a standard USB interface, without the need for each manufacturer > > > of smartcards to provide its own reader or protocol. > > > > > > This gadget driver makes Linux show up as a CCID device to the host and let a > > > userspace daemon act as the smartcard. > > > > > > This is useful when the Linux gadget itself should act as a cryptographic > > > device or forward APDUs to an embedded smartcard device. > > > > > + * Copyright (C) 2018 Marcus Folkesson > > > > > + * > > > > Redundant line > > > > Yep > > > > +static DEFINE_IDA(ccidg_ida); > > > > Where is it destroyed? > > Hm, I'm not sure it needs to be destroyed. From lib/idr.c: > > * You can also use ida_get_new_above() if you need an ID to be allocated > * above a particular number. ida_destroy() can be used to dispose of an > * IDA without needing to free the individual IDs in it. You can use > * ida_is_empty() to find out whether the IDA has any IDs currently allocated. > > > An empty ccidg_ida is the indication that we should clean up our > mess: > > static void ccidg_free_inst(struct usb_function_instance *f) > ... > if (ida_is_empty(&ccidg_ida)) > ccidg_cleanup(); > > If the IDA is empty, should I call ida_destroy() anyway? > Other similiar drivers does not seems to do that. > > I must say that I'm not very familiar with the IDA API. When your module is removed, you need to clean up any remaining memory that the ida used. It's not obvious at all, and is a pain as you would think that if you statically allocate one, like you have here, it would not be needed. You need to just call: ida_destroy(&ccidg_ida); in your module exit function. Hope this helps, greg k-h