From nobody Thu Oct 21 14:32:19 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9207417F7B0C for ; Thu, 21 Oct 2021 14:32:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HZqgl3byTz4XYw for ; Thu, 21 Oct 2021 14:32:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5C95F1C7DC for ; Thu, 21 Oct 2021 14:32:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 19LEWJw3027899 for ; Thu, 21 Oct 2021 14:32:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19LEWJPV027898 for bugs@FreeBSD.org; Thu, 21 Oct 2021 14:32:19 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: bugs@FreeBSD.org Subject: [Bug 259152] [iscsi] OCI oracle iscsi block device problems Date: Thu, 21 Oct 2021 14:32:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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 List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259152 --- Comment #12 from Ed Maste --- (In reply to Dave Cottlehuber from comment #11) Notes from an IRC debugging session with dch@ and andrew@: The panic looks like failed error handling after a reconnect attempt so nee= ds to be fixed but is not the primary issue; this is: WARNING: icl_conn_receive_pdu: received data segment length 16384 is larger than negotiated; dropping connection sys/dev/iscsi/icl_soft.c: len =3D icl_pdu_data_segment_length(request); if (len > ic->ic_max_recv_data_segment_length) { <--- ICL_WARN("received data segment " "length %zd is larger than negotiated; " "dropping connection", len); error =3D EINVAL; break; } ic_max_recv_data_segment_length ultimately gets set by iscsid handling the = new connection. In usr.sbin/iscsid/login.c in login_negotiate_key: } else if (strcmp(name, "MaxRecvDataSegmentLength") =3D=3D 0) { tmp =3D strtoul(value, NULL, 10); if (tmp <=3D 0) log_errx(1, "received invalid " "MaxRecvDataSegmentLength"); if (tmp > isl->isl_max_send_data_segment_length) { log_debugx("capping max_send_data_segment_length " "from %d to %d", tmp, isl->isl_max_send_data_segment_length); tmp =3D isl->isl_max_send_data_segment_length; } conn->conn_max_send_data_segment_length =3D tmp; /* We received target's limit, that means it accepted our's= . */ conn->conn_max_recv_data_segment_length =3D <--- isl->isl_max_recv_data_segment_length; <--- So it appears conn_max_recv_data_segment_length is only set once we receive MaxRecvDataSegmentLength from the target from proxied.pcap, frame 15 our login command contains MaxRecvDataSegmentLength=3D262144 the response is in frame 17 and does not contain MaxRecvDataSegmentLength, = so we never update conn_max_recv_data_segment_length=20 This handling for conn_max_recv_data_segment_length came in with https://cgit.freebsd.org/src/commit/?id=3Da15fbc904a4d535e0c438bcecac056fca= 4fa3c5e --=20 You are receiving this mail because: You are the assignee for the bug.=