Re: [Open-FCoE] Crash in target_report_luns to virtual lun 0.

["Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>]

On Fri, 2012-05-25 at 16:01 +0000, Clark, Steven wrote:
> Never mind.  I found this reported on the target-devel mailing list.   Not an FCoE issue.
> 
> http://article.gmane.org/gmane.linux.scsi.target.devel/1418/match=target_report_luns
> 
> Steve
> 

Hi Steven,

Just noticing this thread (CC' target-devel), and wanted to double check
which kernel this was with..?

Thanks,

--nab


> 
> > -----Original Message-----
> > From: devel-bounces@xxxxxxxxxxxxx [mailto:devel-bounces@xxxxxxxxxxxxx] On Behalf Of Clark, Steven
> > Sent: Thursday, May 24, 2012 6:06 PM
> > To: devel@xxxxxxxxxxxxx
> > Subject: [Open-FCoE] Crash in target_report_luns to virtual lun 0.
> > 
> > I have a target set up in vn2vn mode with two iblock target luns.
> > If I delete either lun 0 or lun 1, a REPORT LUNS command from the client acts as expected.
> > It reports either LUN 1 or LUN 0, whichever is remaining.
> > When I delete both LUNs, so I still have a TPG but no LUNs under it, the target crashes.
> > 
> > The crash is in target_report_luns.  It seems that the data buffer is bad. I'm always sending
> > the report luns command to lun 0.  What's strange is that tpg_virt_lun0 works fine with lun1
> > present but I get the crash when it is not.  I have not been able to figure out what is causing
> > the crash.
> > 
> > Any ideas? Seems like this should be legal as there is still a session, and the virtual lun0 should just report no luns.
> > 
> _______________________________________________
> devel mailing list
> devel@xxxxxxxxxxxxx
> https://lists.open-fcoe.org/mailman/listinfo/devel


--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html