From owner-freebsd-ports-bugs@freebsd.org Fri Jun 1 15:55:43 2018 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C876DF75468 for ; Fri, 1 Jun 2018 15:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5F5D783506 for ; Fri, 1 Jun 2018 15:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1CA6EF7545C; Fri, 1 Jun 2018 15:55:43 +0000 (UTC) Delivered-To: ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC078F7545B for ; Fri, 1 Jun 2018 15:55:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E19683503 for ; Fri, 1 Jun 2018 15:55:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B108511100 for ; Fri, 1 Jun 2018 15:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w51FtfcN037354 for ; Fri, 1 Jun 2018 15:55:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w51Ftfow037352 for ports-bugs@FreeBSD.org; Fri, 1 Jun 2018 15:55:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 227313] net/isboot-kmod works with net/istgt but not with ctld(8) Date: Fri, 01 Jun 2018 15:55:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: milios@ccsys.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2018 15:55:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227313 --- Comment #1 from milios@ccsys.com --- I can confirm I am experiencing this same bug between two FreeBSD 11.1-RELEASE-p10/amd64 systems. I had to apply the same patch to isboot or = else I'd get fatal trap 12 during boot at the point isboot does its thing. Both happen to be VIMAGE kernels though I am running ctld/istgt on the host for = this testing, not a jail. The ctld and istgt daemons are configured identically as far as I can get t= hem (CHAP required, no restriction for initiator name or ip address, one portal group, one target, one LUN of 512 byte blocksize which is the same zvol of = 4096 byte zfs blocksize.) I can confirm CHAP is indeed authenticating in both ca= ses. To be explicit, istgt allows isboot to succeed and ctld doesn't. I get the exact console and log messages as Maurizio. Furthermore, I then enabled DEBUG in the isboot module to get the following console output when booting through ctld: ... ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec iSCSI boot driver version 0.2.13 IS: Initiator name: iqn.2011-11.org.nuos:08-00-27-a7-cb-a7 NIC0: IP address: 192.168.1.71 NIC0: Prefix: 24 NIC0: Gateway: 192.168.1.1 NIC0: MAC address: 08:00:27:a7:cb:a7 TGT0: Target IP address: 23.111.168.34 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2011-11.org.nuos:target0 Boot NIC: em0 Configure IPv4 by NIC0 CHAP Type: CHAP isboot start, thread id=3D186a0 kproc_start Attempting to login to iSCSI target and scan all LUNs. isboot kproc start, thread id=3D186d9 isboot iscsi start, thread id=3D186d9 main loop, thread id=3D186d9 initialize session, thread id=3D186d9 Initiator: iqn.2011-11.org.nuos:08-00-27-a7-cb-a7 Target: iqn.2011-11.org.nuos:target0 Target IP=3D23.111.168.34, Port=3D3260, LUN=3D0 strdup(joe)3 strdup(passwordhere)12 strdup(iqn.2011-11.org.nuos:08-00-27-a7-cb-a7)38 strdup(iqn.2011-11.org.nuos:target0)28 strdup(CHAP,None)9 strdup(None,CRC32C)11 strdup(None,CRC32C)11 isboot_connect open socket try connect...(186d9) wait connect... em0: link state changed to UP old so=3D0, new so=3D0xfffff80006424360 isboot_do_login login start xmit PDU recv PDU isboot_free_mbufext soreceive BHS is not complete, remaining byte(s)=3D48 do login failed boot retry (59) isboot_connect open socket try connect...(186d9) wait connect... em0: link state changed to UP old so=3D0, new so=3D0xfffff80006424000 isboot_do_login login start xmit PDU recv PDU isboot_free_mbufext soreceive BHS is not complete, remaining byte(s)=3D48 do login failed boot retry (58) isboot_connect open socket try connect...(186d9) wait connect... em0: link state changed to UP old so=3D0, new so=3D0xfffff80006423a20 isboot_do_login login start xmit PDU recv PDU isboot_free_mbufext soreceive BHS is not complete, remaining byte(s)=3D48 do login failed boot retry (57) ...repeats... I haven't gone so far as to dig into what's happening on the wire but if I'm asked I'll be glad to follow up with any assistance or testing. --=20 You are receiving this mail because: You are the assignee for the bug.=