linux-kernel - Re: [PATCH 1/3] lkdtm/fortify: Check possible NULL pointer returned by kmalloc()

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] [day] [month] [year] [list]

Message-ID: <Yt5XKEzSz3uAvjCJ@kroah.com>
Date:   Mon, 25 Jul 2022 10:41:12 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Ren Yu <renyu@...china.com>
Cc:     keescook@...omium.org, arnd@...db.de, linux-kernel@...r.kernel.org,
        liqiong@...china.com, yuzhe@...china.com
Subject: Re: [PATCH 1/3] lkdtm/fortify: Check possible NULL pointer returned
 by kmalloc()

On Mon, Jul 25, 2022 at 04:10:00PM +0800, Ren Yu wrote:
> As the possible alloc failure of the kmalloc(),the return pointer
> could be NULL,therefore it should be better to check it.
> 
> Signed-off-by: Ren Yu <renyu@...china.com>
> ---
>  drivers/misc/lkdtm/fortify.c | 3 +++
>  1 file changed, 3 insertions(+)

For some reason this patch series is not properly threaded, so our tools
can not pick them up automatically.  Can you please resend them threaded
properly (git send-email can do this for you)?

thanks,

greg k-h