From: <Christian.Gromm@microchip.com>
To: <erosca@de.adit-jv.com>, <linux-kernel@vger.kernel.org>,
<gregkh@linuxfoundation.org>, <devel@driverdev.osuosl.org>
Cc: <dan.carpenter@oracle.com>, <sudipi@jp.adit-jv.com>,
<o-takashi@sakamocchi.jp>, <colin.king@canonical.com>,
<andrey.shvetsov@k2l.de>, <tiwai@suse.de>,
<roscaeugeniu@gmail.com>, <marcin.s.ciupak@gmail.com>
Subject: Re: [PATCH] staging: most: cdev: fix chrdev_region leak in mod_exit
Date: Thu, 2 May 2019 08:02:56 +0000 [thread overview]
Message-ID: <1556784361.2199.1.camel@microchip.com> (raw)
In-Reply-To: <20190424192343.15418-1-erosca@de.adit-jv.com>
On Mi, 2019-04-24 at 21:23 +0200, Eugeniu Rosca wrote:
> External E-Mail
>
>
> From: Suresh Udipi <sudipi@jp.adit-jv.com>
>
> It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0
> commit [1] missed to fix the memory leak in mod_exit function.
>
> Do it now.
>
> [0] aba258b7310167 ("staging: most: cdev: fix chrdev_region leak")
> [1] https://github.com/microchip-ais/linux/commit/a2d8f7ae7ea381
> ("staging: most: cdev: fix leak for chrdev_region")
>
> Signed-off-by: Suresh Udipi <sudipi@jp.adit-jv.com>
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
Acked-by: Christian Gromm <christian.gromm@microchip.com>
> ---
> drivers/staging/most/cdev/cdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/most/cdev/cdev.c
> b/drivers/staging/most/cdev/cdev.c
> index f2b347cda8b7..d5f236889021 100644
> --- a/drivers/staging/most/cdev/cdev.c
> +++ b/drivers/staging/most/cdev/cdev.c
> @@ -549,7 +549,7 @@ static void __exit mod_exit(void)
> destroy_cdev(c);
> destroy_channel(c);
> }
> - unregister_chrdev_region(comp.devno, 1);
> + unregister_chrdev_region(comp.devno, CHRDEV_REGION_SIZE);
> ida_destroy(&comp.minor_id);
> class_destroy(comp.class);
> }
next prev parent reply other threads:[~2019-05-02 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 19:23 [PATCH] staging: most: cdev: fix chrdev_region leak in mod_exit Eugeniu Rosca
2019-05-01 16:17 ` Greg Kroah-Hartman
2019-05-02 8:02 ` Christian.Gromm [this message]
2019-05-02 17:39 ` Greg Kroah-Hartman
2019-05-03 7:40 ` Eugeniu Rosca
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=1556784361.2199.1.camel@microchip.com \
--to=christian.gromm@microchip.com \
--cc=andrey.shvetsov@k2l.de \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.s.ciupak@gmail.com \
--cc=o-takashi@sakamocchi.jp \
--cc=roscaeugeniu@gmail.com \
--cc=sudipi@jp.adit-jv.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.