[stgt] [RESEND] [PATCH] Fix for segfault in tgtd sendtargets
arne.redlich at googlemail.com
Tue Apr 21 09:35:13 CEST 2009
Am Dienstag, den 21.04.2009, 05:46 +0100 schrieb Chris Webb:
> If we hardcode this sendtargets limit, can we make sure it's something
> bigger than 8192? A iSCSI target daemon that silently fails to export more
> than 70 targets is okay for small-scale tests but not much more than that.
No. And in fact even hardwiring it to 8k could potentially lead to
problems already, it's just very unlikely.
As I wrote before: to get it right (i.e. support an arbitrarily long
list of targets), the data must be split into several PDUs, each having
a max size of the MaxRecvDSL the initiator declared. And sequencing of
these PDUs is also different from SCSI Data In's, i.e. the first text
rsp is sent with a tag indicating there is more data, and the initiator
can then choose to request the next part of the response with another
We have support for that in IET trunk - given TGTs roots it might be
possible to port it.
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt