From: Christoph Hellwig <hch@infradead.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Dick Kennedy <dick.kennedy@broadcom.com>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
kernel-janitors@vger.kernel.org,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Paul Ely <paul.ely@broadcom.com>, Hannes Reinecke <hare@suse.de>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH resend] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler()
Date: Wed, 20 May 2020 17:37:52 +0000 [thread overview]
Message-ID: <20200520173752.GA13546@infradead.org> (raw)
In-Reply-To: <yq1y2pmtsv7.fsf@ca-mkp.ca.oracle.com>
On Wed, May 20, 2020 at 01:33:12PM -0400, Martin K. Petersen wrote:
>
> Christoph,
>
> > On Wed, May 20, 2020 at 08:24:33PM +0300, Dan Carpenter wrote:
> >> On Wed, May 20, 2020 at 09:55:57AM -0700, Christoph Hellwig wrote:
> >> > James, can you review this patch?
> >>
> >> He already reviewed it in a different thread. I copied his R-b tag.
> >
> > James, should this go into the nvme or scsi tree?
>
> The offending patch is in the nvme tree so I think you should take
> it. Otherwise I'll pick it up in 5.8/scsi-fixes.
I'll pick it up. Can you give me an ACK for it to show Jens you are
ok with that?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Dick Kennedy <dick.kennedy@broadcom.com>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
kernel-janitors@vger.kernel.org,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@infradead.org>,
Paul Ely <paul.ely@broadcom.com>, Hannes Reinecke <hare@suse.de>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH resend] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler()
Date: Wed, 20 May 2020 10:37:52 -0700 [thread overview]
Message-ID: <20200520173752.GA13546@infradead.org> (raw)
In-Reply-To: <yq1y2pmtsv7.fsf@ca-mkp.ca.oracle.com>
On Wed, May 20, 2020 at 01:33:12PM -0400, Martin K. Petersen wrote:
>
> Christoph,
>
> > On Wed, May 20, 2020 at 08:24:33PM +0300, Dan Carpenter wrote:
> >> On Wed, May 20, 2020 at 09:55:57AM -0700, Christoph Hellwig wrote:
> >> > James, can you review this patch?
> >>
> >> He already reviewed it in a different thread. I copied his R-b tag.
> >
> > James, should this go into the nvme or scsi tree?
>
> The offending patch is in the nvme tree so I think you should take
> it. Otherwise I'll pick it up in 5.8/scsi-fixes.
I'll pick it up. Can you give me an ACK for it to show Jens you are
ok with that?
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
Dick Kennedy <dick.kennedy@broadcom.com>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
kernel-janitors@vger.kernel.org, Paul Ely <paul.ely@broadcom.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH resend] scsi: lpfc: Fix a use after free in lpfc_nvme_unsol_ls_handler()
Date: Wed, 20 May 2020 10:37:52 -0700 [thread overview]
Message-ID: <20200520173752.GA13546@infradead.org> (raw)
In-Reply-To: <yq1y2pmtsv7.fsf@ca-mkp.ca.oracle.com>
On Wed, May 20, 2020 at 01:33:12PM -0400, Martin K. Petersen wrote:
>
> Christoph,
>
> > On Wed, May 20, 2020 at 08:24:33PM +0300, Dan Carpenter wrote:
> >> On Wed, May 20, 2020 at 09:55:57AM -0700, Christoph Hellwig wrote:
> >> > James, can you review this patch?
> >>
> >> He already reviewed it in a different thread. I copied his R-b tag.
> >
> > James, should this go into the nvme or scsi tree?
>
> The offending patch is in the nvme tree so I think you should take
> it. Otherwise I'll pick it up in 5.8/scsi-fixes.
I'll pick it up. Can you give me an ACK for it to show Jens you are
ok with that?
next prev parent reply other threads:[~2020-05-20 17:37 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
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 [this message]
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=20200520173752.GA13546@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dan.carpenter@oracle.com \
--cc=dick.kennedy@broadcom.com \
--cc=hare@suse.de \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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.