From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: RUC_SoftSec <rucsoftsec@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Wang YanQing <udknight@gmail.com>,
Dave Airlie <airlied@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] tty: Add NULL check to return value of kzalloc()
Date: Mon, 28 Oct 2013 08:20:34 -0700 [thread overview]
Message-ID: <20131028152034.GA9437@kroah.com> (raw)
In-Reply-To: <1382938072-14769-1-git-send-email-rucsoftsec@gmail.com>
On Mon, Oct 28, 2013 at 01:27:52PM +0800, RUC_SoftSec wrote:
> Function kzalloc() may return a NULL pointer, it should be checked against NULL before used.
> This bug is found by a static analysis tool developed by RUC_SoftSec, supported by China.X.Orion.
>
> Signed-off-by: RUC_SoftSec <rucsoftsec@gmail.com>
I've already explained why I can not accept patches like this, consider
all of them that you sent now deleted from my inbox.
greg k-h
prev parent reply other threads:[~2013-10-28 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 5:27 [PATCH 1/1] tty: Add NULL check to return value of kzalloc() RUC_SoftSec
2013-10-28 15:20 ` Greg Kroah-Hartman [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=20131028152034.GA9437@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rucsoftsec@gmail.com \
--cc=udknight@gmail.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