From: Greg KH <gregkh@linuxfoundation.org>
To: Ren Yu <renyu@nfschina.com>
Cc: keescook@chromium.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, liqiong@nfschina.com,
yuzhe@nfschina.com
Subject: Re: [PATCH 1/3] lkdtm/fortify: Check possible NULL pointer returned by kmalloc()
Date: Mon, 25 Jul 2022 10:41:12 +0200 [thread overview]
Message-ID: <Yt5XKEzSz3uAvjCJ@kroah.com> (raw)
In-Reply-To: <20220725081000.19407-1-renyu@nfschina.com>
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@nfschina.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
prev parent reply other threads:[~2022-07-25 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 8:10 Ren Yu
2022-07-25 8:41 ` Greg KH [this message]
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=Yt5XKEzSz3uAvjCJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=renyu@nfschina.com \
--cc=yuzhe@nfschina.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
all inboxes | Powered by JetHome®