public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: Destroy uio_idr on module exit
Date: Fri, 10 Jul 2015 17:03:43 -0700	[thread overview]
Message-ID: <20150711000343.GA30309@kroah.com> (raw)
In-Reply-To: <mqdegkhu8qj.fsf@c203.arch.suse.de>

On Thu, Jul 09, 2015 at 08:48:36AM +0200, Johannes Thumshirn wrote:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> 
> > On Wed, Jul 08, 2015 at 05:24:46PM +0200, Johannes Thumshirn wrote:
> >> Destroy uio_idr on module exit, reclaiming the allocated memory.
> >> 
> >> This was detected by the following semantic patch (written by Luis Rodriguez
> >> <mcgrof@suse.com>)
> >> <SmPL>
> >> @ defines_module_init @
> >> declarer name module_init, module_exit;
> >> declarer name DEFINE_IDR;
> >> identifier init;
> >> @@
> >> 
> >> module_init(init);
> >> 
> >> @ defines_module_exit @
> >> identifier exit;
> >> @@
> >> 
> >> module_exit(exit);
> >> 
> >> @ declares_idr depends on defines_module_init && defines_module_exit @
> >> identifier idr;
> >> @@
> >> 
> >> DEFINE_IDR(idr);
> >> 
> >> @ on_exit_calls_destroy depends on declares_idr && defines_module_exit @
> >> identifier declares_idr.idr, defines_module_exit.exit;
> >> @@
> >> 
> >> exit(void)
> >> {
> >>  ...
> >>  idr_destroy(&idr);
> >>  ...
> >> }
> >> 
> >> @ missing_module_idr_destroy depends on declares_idr && defines_module_exit && !on_exit_calls_destroy @
> >> identifier declares_idr.idr, defines_module_exit.exit;
> >> @@
> >> 
> >> exit(void)
> >> {
> >>  ...
> >>  +idr_destroy(&idr);
> >> }
> >> 
> >> </SmPL>
> >> 
> >> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> >
> > Nice work.  Shouldn't we do the same thing for ida_destroy() as well?  I
> > see 4 USB drivers that need this same fix for that structure.
> >
> 
> Can you tell me which? I've send overall 13 patches for this (no series
> as get_maintainers.pl for the series spit out > 30 Recipients so I
> refused to send spam).
> 
> Maybe/probably I forgot one (or two).

You need to look for "ida_destroy" not just "idr_destroy", here's the
ones I found in just a few seconds of looking:

~/linux/gregkh $ cd drivers/usb/
~/linux/gregkh/drivers/usb $ cg ida_destroy
~/linux/gregkh/drivers/usb $ cg DEFINE_IDA
0 chipidea/core.c             597 static DEFINE_IDA(ci_ida);
1 gadget/function/f_hid.c      31 static DEFINE_IDA(hidg_ida);
2 gadget/function/f_printer.c  60 static DEFINE_IDA(printer_ida);
3 gadget/function/rndis.c      67 static DEFINE_IDA(rndis_ida);

There's 4 users that never free memory when the module is unloaded for
the ida structure.

thanks,

greg k-h

      reply	other threads:[~2015-07-11  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 15:24 [PATCH] uio: Destroy uio_idr on module exit Johannes Thumshirn
2015-07-08 17:24 ` Greg Kroah-Hartman
2015-07-09  6:48   ` Johannes Thumshirn
2015-07-11  0:03     ` Greg Kroah-Hartman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150711000343.GA30309@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hjk@hansjkoch.de \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox