netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pakki001@umn.edu
Cc: kjlu@umn.edu, shshaikh@marvell.com, manishc@marvell.com,
	GR-Linux-NIC-Dev@marvell.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] qlcnic: Avoid potential NULL pointer dereference
Date: Fri, 15 Mar 2019 11:56:40 -0700 (PDT)	[thread overview]
Message-ID: <20190315.115640.1477522812438525683.davem@davemloft.net> (raw)
In-Reply-To: <20190314203140.20039-1-pakki001@umn.edu>

From: Aditya Pakki <pakki001@umn.edu>
Date: Thu, 14 Mar 2019 15:31:40 -0500

> netdev_alloc_skb can fail and return a NULL pointer which is
> dereferenced without a check. The patch avoids such a scenario.
> 
> Signed-off-by: Aditya Pakki <pakki001@umn.edu>

Applied.

  reply	other threads:[~2019-03-15 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 20:31 [PATCH] qlcnic: Avoid potential NULL pointer dereference Aditya Pakki
2019-03-15 18:56 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-14 20:26 Aditya Pakki

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=20190315.115640.1477522812438525683.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=kjlu@umn.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pakki001@umn.edu \
    --cc=shshaikh@marvell.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;
as well as URLs for NNTP newsgroup(s).