Re: [PATCH v2 04/20] lpfc: Fix oops when NVME Target is discovered in a nonNVME environment

2017-08-07 Thread James Smart
On 8/7/2017 1:00 AM, Johannes Thumshirn wrote: On Fri, Aug 04, 2017 at 05:47:15PM -0700, James Smart wrote: From: Dick Kennedy lpfc oops when it discovers a NVME target but is configured for SCSI only operation. Oops is in lpfc_nvme_register_port+0x33/0x300. Why

Re: [PATCH v2 04/20] lpfc: Fix oops when NVME Target is discovered in a nonNVME environment

2017-08-07 Thread Johannes Thumshirn
On Fri, Aug 04, 2017 at 05:47:15PM -0700, James Smart wrote: > From: Dick Kennedy > > lpfc oops when it discovers a NVME target but is configured for SCSI > only operation. Oops is in lpfc_nvme_register_port+0x33/0x300. Why does it even call lpfc_nvme_register_rport

[PATCH v2 04/20] lpfc: Fix oops when NVME Target is discovered in a nonNVME environment

2017-08-04 Thread James Smart
From: Dick Kennedy lpfc oops when it discovers a NVME target but is configured for SCSI only operation. Oops is in lpfc_nvme_register_port+0x33/0x300. The localport is not valid so it should not have been referenced. Added validity check for localport Signed-off-by: