[EXT] Re: [PATCH v2] nvme-fc: initialize nvme fc ctrl ops

[Niklas Cassel]

On Wed, Feb 22, 2023 at 05:59:54AM +0000, Nilesh Javali wrote:
> Christoph,
> 
> Thanks for pointing to the commit.
> I do not see this commit in Martin's tree 6.3/scsi-staging or 6.3/scsi-queue branches.
> 
> Martin,
> 
> The 6.3/scsi-staging or 6.3/scsi-queue branches are still at 6.2.0-rc1.
> That could be the reason we hit the NVMe discovery NULL pointer dereference issue.
> Any plans to pull the below commit to 6.3/scsi-staging or 6.3/scsi-queue branches.
> Or am I missing something here.

Hello Nilesh,

What you are missing is that NVMe is not SCSI :)

Consult the MAINTAINER file to see the correct (git) tree to climb:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v6.2#n14922

While SCSI sends pull requests straight to Linus,
NVMe sends pull requests first to Jens, who then sends it to Linus.


Kind regards,
Niklas

> 
> Thanks,
> Nilesh
> 
> > -----Original Message-----
> > From: Christoph Hellwig <hch at lst.de>
> > Sent: Tuesday, February 21, 2023 11:05 PM
> > To: Nilesh Javali <njavali at marvell.com>
> > Cc: linux-nvme at lists.infradead.org; martin.petersen at oracle.com; linux-
> > scsi at vger.kernel.org; GR-QLogic-Storage-Upstream <GR-QLogic-Storage-
> > Upstream at marvell.com>; Bikash Hazarika <bhazarika at marvell.com>; Anil
> > Gurumurthy <agurumurthy at marvell.com>; Shreyas Deodhar
> > <sdeodhar at marvell.com>; Christoph Hellwig <hch at lst.de>
> > Subject: [EXT] Re: [PATCH v2] nvme-fc: initialize nvme fc ctrl ops
> > 
> > External Email
> > 
> > ----------------------------------------------------------------------
> > On Tue, Feb 21, 2023 at 01:57:08AM -0800, Nilesh Javali wrote:
> > > CPU: 61 PID: 6064 Comm: nvme Kdump: loaded Not tainted 6.2.0-rc1 #3
> > 
> > Well, that's a reall old -rc.
> > 
> > This should be fixed by:
> > 
> > commit 98e3528012cd571c48bbae7c7c0f868823254b6c
> > Author: Ross Lagerwall <ross.lagerwall at citrix.com>
> > Date:   Fri Jan 20 17:43:54 2023 +0000
> > 
> >     nvme-fc: fix initialization order
>