Hi Chris, thx for your time and giving this detailed descriptions.
just tested your patch and it works fine for me with a 4.4.x 64bit kernel. f.y.i. debuglog ******************************** .... iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: created new iSCSI session sid 2 host no 7 iscsid: in kcreate_conn iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: created new iSCSI connection 2:0 iscsid: in kbind_conn iscsid: in __kipc_call iscsid: in kwritev iscsid: in nlpayload_read iscsid: in nlpayload_read iscsid: bound iSCSI connection 2:0 to session 2 .... ********************************** On Thu, 9 Feb 2017 11:44:51 -0500 (EST) Chris Leech <cle...@redhat.com> wrote: > I'm curious as to what would prevent you from running a 64-bit iscsid > in this case, but that's OK. You are totally right this would be the best and safest solution. I will do this in the future, but the complete switch from 32 to 64 depends on other stuff like changing to another buildsystem and stuff like that, that needs to be done first. So I have to find a "in-between-solution". Greetz Matze -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
