linux-kernel - Re: [PATCH -next 0/2] A few fixup patches for nvmem

lists.openwall.net		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 linux-hardening linux-cve-announce 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:   Wed, 17 Aug 2022 09:53:20 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Gaosheng Cui <cuigaosheng1@...wei.com>, gregkh@...uxfoundation.org
Cc:     linux-kernel@...r.kernel.org, wangweiyang2@...wei.com
Subject: Re: [PATCH -next 0/2] A few fixup patches for nvmem



On 16/08/2022 14:49, Gaosheng Cui wrote:
> This series contains a fixup patches to fix possible memleak,
> and add error handling of dev_set_name to keep nvmem code
> implementation consistent, in addition, it can also avoid
> the possibility illegal address access. Thanks!
> 
> Gaosheng Cui (2):
>    nvmem: core: Fix memleak in nvmem_register()
>    nvmem: core: add error handling for dev_set_name
> 

I have applied these patches for now but remember the subject line does 
not reflect the patch version or the cover letter does not include any 
changes done over the versions.

Please take a look at 
https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html


thanks,
Srini

>   drivers/nvmem/core.c | 27 +++++++++++++++------------
>   1 file changed, 15 insertions(+), 12 deletions(-)
>