linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Himanshu Madhani <hmadhani@marvell.com>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	jejb@linux.ibm.com, linux-kernel@vger.kernel.org,
	Allen Pais <allen.pais@oracle.com>
Subject: Re: [PATCH] qla2xxx: fix a potential NULL pointer dereference
Date: Thu, 03 Oct 2019 21:56:34 -0400	[thread overview]
Message-ID: <yq1h84ps27h.fsf@oracle.com> (raw)
In-Reply-To: <1568824618-4366-1-git-send-email-allen.pais@oracle.com> (Allen Pais's message of "Wed, 18 Sep 2019 22:06:58 +0530")


> alloc_workqueue is not checked for errors and as a result,
> a potential NULL dereference could occur.

Himanshu: Please review!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-10-04  1:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 16:36 [PATCH] qla2xxx: fix a potential NULL pointer dereference Allen Pais
2019-10-04  1:56 ` Martin K. Petersen [this message]
2019-10-04  6:10 ` Martin Wilck
2019-10-10  2:29 ` Martin K. Petersen

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=yq1h84ps27h.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=allen.pais@oracle.com \
    --cc=hmadhani@marvell.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).