From: Arnd Bergmann <arnd@arndb.de>
To: Jann Horn <jann@thejh.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
linux-kernel@vger.kernel.org, linux-parport@lists.infradead.org,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH v2] ppdev: fix double-free of pp->pdev->name
Date: Thu, 10 Nov 2016 14:18:12 +0100 [thread overview]
Message-ID: <2721049.iK2v6rcyvW@wuerfel> (raw)
In-Reply-To: <1477865964-4497-1-git-send-email-jann@thejh.net>
On Sunday, October 30, 2016 11:19:24 PM CET Jann Horn wrote:
> diff --git a/drivers/char/ppdev.c b/drivers/char/ppdev.c
> index d23368874710..6af1ce04b3da 100644
> --- a/drivers/char/ppdev.c
> +++ b/drivers/char/ppdev.c
> @@ -748,10 +748,7 @@ static int pp_release(struct inode *inode, struct file *file)
> }
>
> if (pp->pdev) {
> - const char *name = pp->pdev->name;
> -
> parport_unregister_device(pp->pdev);
> - kfree(name);
> pp->pdev = NULL;
> pr_debug(CHRDEV "%x: unregistered pardevice\n", minor);
> }
>
I took a closer look at this and found that we also leak the name
that is passed in register_device() in the same file:
name = kasprintf(GFP_KERNEL, CHRDEV "%x", minor);
...
pdev = parport_register_dev_model(port, name, &ppdev_cb, minor);
parport_register_dev_model() copies the name using kstrdup() and
we should really free it after parport_register_dev_model().
It's not a huge problem, just leaking a few bytes of memory, but
the extra kfree() probably came from this confusion.
Arnd
next prev parent reply other threads:[~2016-11-10 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 22:19 [PATCH v2] ppdev: fix double-free of pp->pdev->name Jann Horn
2016-11-10 6:57 ` Greg Kroah-Hartman
2016-11-10 12:40 ` Sudip Mukherjee
2016-11-10 13:18 ` Arnd Bergmann [this message]
2016-11-10 13:50 ` Sudip Mukherjee
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=2721049.iK2v6rcyvW@wuerfel \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jann@thejh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=luto@amacapital.net \
--cc=sudipm.mukherjee@gmail.com \
/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