From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aditya Pakki <pakki001@umn.edu>
Cc: devel@driverdev.osuosl.org, kjlu@umn.edu,
linux-kernel@vger.kernel.org,
Sabin Mihai Rapan <sabin.rapan@gmail.com>,
Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: [PATCH v2] staging: rtlwifi: rtl8822b: fix to avoid NULL pointer dereference
Date: Wed, 20 Mar 2019 08:23:57 +0100 [thread overview]
Message-ID: <20190320072357.GB2647@kroah.com> (raw)
In-Reply-To: <20190319202127.16692-1-pakki001@umn.edu>
On Tue, Mar 19, 2019 at 03:21:25PM -0500, Aditya Pakki wrote:
> skb allocated via dev_alloc_skb can fail and return a NULL pointer.
> This patch avoids such a scenario and returns, consistent with other
> invocations.
>
> ---
> v1: Patch collision with rtl_phydm.c, fix as per Greg
> Signed-off-by: Aditya Pakki <pakki001@umn.edu>
Same here, has to be above.
next prev parent reply other threads:[~2019-03-20 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:21 [PATCH v2] staging: rtlwifi: rtl8822b: fix to avoid NULL pointer dereference Aditya Pakki
2019-03-20 7:23 ` Greg Kroah-Hartman [this message]
2019-03-20 7:24 ` Greg Kroah-Hartman
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=20190320072357.GB2647@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=pakki001@umn.edu \
--cc=sabin.rapan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.