lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 2 May 2019 19:39:20 +0200
From:   Greg Kroah-Hartman <>
To:     Eugeniu Rosca <>
Cc:     Christian Gromm <>,,,
        Andrey Shvetsov <>,
        Dan Carpenter <>,
        Colin Ian King <>,
        Takashi Sakamoto <>,
        Takashi Iwai <>,
        Marcin Ciupak <>,
        Suresh Udipi <>,
        Eugeniu Rosca <>
Subject: Re: [PATCH] staging: most: cdev: fix chrdev_region leak in mod_exit

On Wed, Apr 24, 2019 at 09:23:43PM +0200, Eugeniu Rosca wrote:
> From: Suresh Udipi <>
> 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]
>     ("staging: most: cdev: fix leak for chrdev_region")
> Signed-off-by: Suresh Udipi <>
> Signed-off-by: Eugeniu Rosca <>
> Acked-by: Christian Gromm <>

In the future, please use the "correct" way to mark a fixup patch.  For
this, it would be:
Fixes: aba258b73101 ("staging: most: cdev: fix chrdev_region leak")

I'll go add it, and the needed stable tag to the patch when applying it.


greg k-h

Powered by blists - more mailing lists