From nobody Sun Dec 24 15:50:38 2023 X-Original-To: fs@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 4Sylqf1kLyz54nQ5 for ; Sun, 24 Dec 2023 15:50:38 +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 4Sylqf0hFMz4Q60 for ; Sun, 24 Dec 2023 15:50:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1703433038; a=rsa-sha256; cv=none; b=lxslbA8fTCXig0TtRDkc036VPWHuO/8wIkjMJM4WjRY/4O1WCY7jkgCBcdqsW2JnFHqLxC vPSKsr0Wlb0dQvMF3tKeKpgEKBagAEORhIUS72vOkOEYEFlP+Nj+xByW+b/QHBoYJ3itDG xGpgzVs8kTu1RN3AL25g0odsqsmTi5WDfZa3/oS1nbTga8FSyCzEx8g9D58+5dn/p3QhLD NJk1WVuhFcwwvwgp3TMPzmdOEN3l6IhiwJvTLKbvtrb8t110If9ourNBAU8Dkfz3VlDKVs bujqONVjIrquKnvKrH9JJ/+aZbxXhuNJt8jw13k/h5Ki6gIQKbsboaeg2RJJcA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1703433038; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TW+oWNB3T+iVXjpN16/fJPLk3wf65VcZndL5v+aAOdU=; b=NnsmkUUj6xQVN+WK0pMaV8nxl4lyQK1hcm70W9KehWYO/vPbmF/cJ2xZW4+dga0v3SXa/s ph4deeB3HZBBqmQ83vTeXY+42yPlw939HHSWXLDBGrmX3fPhJZEwXgxfbSP3K9ZePusYi5 NFUS7xwkz7xkzBpxa/VvI+/Oihwc9pW1woD1Lxqjpj/wWuKV/gF/aKzyrYYsMSjCZOHk38 deAheHPgFGqVRWsyfmn/QKLimYTjcvEFtkU28kqWYzixix1Zy3FA3cEDqpS3KIKLxjyONX gDaFuL3RkOOJKoG9vrtVc7PfYrCMJ0jyGYn+qlD/y+aOGnjL295Oevq50VivMQ== 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 4Sylqd6tGTzZ90 for ; Sun, 24 Dec 2023 15:50:37 +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 3BOFob2D099023 for ; Sun, 24 Dec 2023 15:50:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3BOFobW0099022 for fs@FreeBSD.org; Sun, 24 Dec 2023 15:50:37 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: fs@FreeBSD.org Subject: [Bug 275905] nfs client: mount becomes unresponsive Date: Sun, 24 Dec 2023 15:50:38 +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: 14.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@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: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275905 --- Comment #4 from Rick Macklem --- The renew thread RPC (the one that your backtrace shows as hung in nfsv4_sequencelookup()) would be using the host/FQDN@REALM entry in the default /etc/krb5.keytab. (ie. Your TGT would not be used for this, since the renew thread runs as "root".) Could the client's keytab entry be broken somehow? (As you probably are aware, when you create a new keytab for a principal, old keytabs no longer work.) You could go onto the client and do # kinit -k host/FQDN to see that the keytab entry for "host" works ok. (I am still wondering what will happen if the TGT for the keytab expires just after the RPC request is sent to the server. I'll look into that.) There could also be a problem where other RPCs were using all slots, so the renew thread slept in nfsv4_sequencelookup() and then another thread needed the renew thread to do some work. --> The renew thread should really have a dedicated slot in the NFSv4 session, so that no other thread can cause it to block. --> I might work on a patch for that. Does this hang occur frequently or was this a "one time" hang on a mount that usually behaves ok? --=20 You are receiving this mail because: You are the assignee for the bug.=