All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: James Smart <james.smart@broadcom.com>,
	Dick Kennedy <dick.kennedy@broadcom.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
	Paul Ely <paul.ely@broadcom.com>,
	linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler()
Date: Fri, 15 May 2020 00:21:30 +0000	[thread overview]
Message-ID: <yq1y2purqt1.fsf@oracle.com> (raw)
In-Reply-To: <20200512181909.GA299091@mwanda> (Dan Carpenter's message of "Tue, 12 May 2020 21:19:09 +0300")


Dan,

> The "axchg" pointer is dereferenced when we call the
> lpfc_nvme_unsol_ls_issue_abort() function.  It can't be either freed or
> NULL.
>
> Fixes: 3a8070c567aa ("lpfc: Refactor NVME LS receive handling")

This fix needs to go through the NVMe tree.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: James Smart <james.smart@broadcom.com>,
	Dick Kennedy <dick.kennedy@broadcom.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
	Paul Ely <paul.ely@broadcom.com>,
	linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler()
Date: Thu, 14 May 2020 20:21:30 -0400	[thread overview]
Message-ID: <yq1y2purqt1.fsf@oracle.com> (raw)
In-Reply-To: <20200512181909.GA299091@mwanda> (Dan Carpenter's message of "Tue, 12 May 2020 21:19:09 +0300")


Dan,

> The "axchg" pointer is dereferenced when we call the
> lpfc_nvme_unsol_ls_issue_abort() function.  It can't be either freed or
> NULL.
>
> Fixes: 3a8070c567aa ("lpfc: Refactor NVME LS receive handling")

This fix needs to go through the NVMe tree.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2020-05-15  0:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 18:19 [PATCH] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler() Dan Carpenter
2020-05-12 18:19 ` Dan Carpenter
2020-05-14 17:03 ` James Smart
2020-05-14 17:03   ` James Smart
2020-05-15  0:21 ` Martin K. Petersen [this message]
2020-05-15  0:21   ` Martin K. Petersen
2020-05-15 10:19   ` [PATCH resend] " Dan Carpenter
2020-05-15 10:19     ` Dan Carpenter
2020-05-15 10:19     ` Dan Carpenter
2020-05-20 16:55     ` Christoph Hellwig
2020-05-20 16:55       ` Christoph Hellwig
2020-05-20 16:55       ` Christoph Hellwig
2020-05-20 17:24       ` Dan Carpenter
2020-05-20 17:24         ` Dan Carpenter
2020-05-20 17:24         ` Dan Carpenter
2020-05-20 17:28         ` Christoph Hellwig
2020-05-20 17:28           ` Christoph Hellwig
2020-05-20 17:28           ` Christoph Hellwig
2020-05-20 17:33           ` Martin K. Petersen
2020-05-20 17:33             ` Martin K. Petersen
2020-05-20 17:33             ` Martin K. Petersen
2020-05-20 17:37             ` Christoph Hellwig
2020-05-20 17:37               ` Christoph Hellwig
2020-05-20 17:37               ` Christoph Hellwig
2020-05-20 17:39               ` Martin K. Petersen
2020-05-20 17:39                 ` Martin K. Petersen
2020-05-20 17:39                 ` Martin K. Petersen
2020-05-20 17:48                 ` Christoph Hellwig
2020-05-20 17:48                   ` Christoph Hellwig
2020-05-20 17:48                   ` Christoph Hellwig
2020-05-20 17:51                   ` James Smart
2020-05-20 17:51                     ` James Smart
2020-05-20 17:51                     ` James Smart
2020-05-20 17:57                     ` Christoph Hellwig
2020-05-20 17:57                       ` Christoph Hellwig
2020-05-20 17:57                       ` Christoph Hellwig
2020-05-20 18:01                     ` Dan Carpenter
2020-05-20 18:01                       ` Dan Carpenter
2020-05-20 18:01                       ` Dan Carpenter

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=yq1y2purqt1.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=dan.carpenter@oracle.com \
    --cc=dick.kennedy@broadcom.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=jejb@linux.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=paul.ely@broadcom.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.