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. Thanks, Nilesh > -----Original Message----- > From: Christoph Hellwig <hch@xxxxxx> > Sent: Tuesday, February 21, 2023 11:05 PM > To: Nilesh Javali <njavali@xxxxxxxxxxx> > Cc: linux-nvme@xxxxxxxxxxxxxxxxxxx; martin.petersen@xxxxxxxxxx; linux- > scsi@xxxxxxxxxxxxxxx; GR-QLogic-Storage-Upstream <GR-QLogic-Storage- > Upstream@xxxxxxxxxxx>; Bikash Hazarika <bhazarika@xxxxxxxxxxx>; Anil > Gurumurthy <agurumurthy@xxxxxxxxxxx>; Shreyas Deodhar > <sdeodhar@xxxxxxxxxxx>; Christoph Hellwig <hch@xxxxxx> > 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@xxxxxxxxxx> > Date: Fri Jan 20 17:43:54 2023 +0000 > > nvme-fc: fix initialization order
