Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp808225pxj; Thu, 27 May 2021 12:06:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwbEYOw53qfp3m9f10Ij1wsNBxAZxHczIEiOxzysWc/S8q5BoyAkt1Cel3TN0J4pTmXwgNK X-Received: by 2002:a05:6e02:f50:: with SMTP id y16mr3916955ilj.61.1622142411025; Thu, 27 May 2021 12:06:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622142411; cv=none; d=google.com; s=arc-20160816; b=ZbkcrNF4Y0kRQ4K8Y/FNZUiA/MYpak1cY7Ei2vevP5W78X0AZ0WkP1S8bRDQ6NaQ5D FEnuyPgX1CLGQdZxQxSypcNg5uJP4glz0qzmb8Vf83Iel6yvPL2z36s1R/2blbiAh6rn dwMhS5yRIVMaci/Af24Wo+HoFpKPro5nSgth2aGSzy9quw105H2RgewPtsRLakeRrZvo rRquTE8PZ10EprYawPvT6kDLslLTpn60uCqlRqqP89YkreOeKT3aK9a7nIdOUavaZSST KoKZf7FkuHXS1XDm3kr3aQ7t0XPBRVDP5fFpDeRBc+ksk4tvWSjLwkDWuMbCeTTVDsHv whcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:to:from:dkim-signature; bh=de/Y/qlIvfzMz0jKsKeUXwFze4xGleIcl6uqoXpcELc=; b=kMX1o3VgQi9q7NNnTTM/P+5IF/94HvbgfPuDGBFpWiBEJLepCYVO5VOIm9/iEF2jjE v8YoogXvo7pZD0koWvAe4UTGk4SgeyeSBJtKWIeILqkpDAFMMcssNF4rvKO3gFzT7xyi vu8i+50OquIWAPupwtQA6n8h4zGHM59cE79ahq9vjnO3do3tuLhBTOLBvhb73zjclXtk iFuRg2gaAs0vCrHLPEe2hNdKXXUOOa3qWLj3En1OdqG5wW1hMNULDuh8NDb1IcUbMC4N MQ/HnuxWyAq8P9oQQhe0S98cNGAa+6jlasQMOM8B6+tbpc7JMt5ggPFL177hyqPEOxY9 hodw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OOBsgkd5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y196si3588804iof.24.2021.05.27.12.06.37; Thu, 27 May 2021 12:06:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OOBsgkd5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234155AbhE0SeR (ORCPT + 99 others); Thu, 27 May 2021 14:34:17 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:58598 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235787AbhE0SeQ (ORCPT ); Thu, 27 May 2021 14:34:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1622140362; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=de/Y/qlIvfzMz0jKsKeUXwFze4xGleIcl6uqoXpcELc=; b=OOBsgkd5B6bBBa8b6QwqfRY8aObnk566RZzerdIix84EeDT11t49JQ3TiT3M8PJMpCWuX2 KFZJLb4L+QzVRqOylFh2wYZ+dw67044lUdJ09eKEiYXZucYcAAip7geBdYX38w3jTiL2j5 21HlqvQFuCnOS/bcYV9pzHXxJ8l2+yk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-374-vstTTJXNPbqrN2GYu1i66g-1; Thu, 27 May 2021 14:32:40 -0400 X-MC-Unique: vstTTJXNPbqrN2GYu1i66g-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C90091903100 for ; Thu, 27 May 2021 18:32:39 +0000 (UTC) Received: from aion.usersys.redhat.com (ovpn-114-18.rdu2.redhat.com [10.10.114.18]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AF37F6061F for ; Thu, 27 May 2021 18:32:39 +0000 (UTC) Received: by aion.usersys.redhat.com (Postfix, from userid 1000) id F2C491A003D; Thu, 27 May 2021 14:32:38 -0400 (EDT) From: Scott Mayhew To: linux-nfs@vger.kernel.org Subject: [nfs-utils PATCH v2 0/2] Two rpc.gssd improvements Date: Thu, 27 May 2021 14:32:36 -0400 Message-Id: <20210527183238.584349-1-smayhew@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Changes since v1: - Replaced the upcall_thread_info.cancelled field with a flags field, to facilitate having the watchdog thread print an error message only once for each timed-out upcall thread. - Removed the "created thread id" log message. - Added missing break when parsing the "-C" option. - Added some comments. These patches provide the following improvements for rpc.gssd: 1) deal with failed thread creation 2) add a timeout for upcall threads Both of these issues can leave kernel mount processes hanging indefinitely. A timeout was originally proposed in the kernel (https://lore.kernel.org/linux-nfs/20180618172542.45519-1-steved@redhat.com/) but this approach was rejected by Trond: I'm saying that we can do this entirely in userland without any kernel changes. As long as that hasn't been attempted and proven to be flawed, then there is no reason to accept any kernel patches. So this is my attempt at doing the timeout in userland. The first patch was tested using a program that intercepts clone() and changes the return code to -EAGAIN. For the second patch, I have two different tests I've been running: 1) In an IPA domain in our lab, I have a server running 100 kerberized nfsd containers. The client has mountpoints to all 100 of those servers defined in its /etc/fstab. I run 'systemctl start remote-fs.target' to kick off all those mounts in parallel, while running the following systemtap script to periodically mess with the mount processes: ---8<--- global i probe begin { i=0 } probe process("/lib64/libgssapi_krb5.so.2").function("gss_acquire_cred") { if (++i % 100 == 0) { printf("delay (i=%d)\n", i) mdelay(30000) } } ---8<--- I actually run the test in a loop... the driver script looks like this: ---8<--- #!/bin/bash let i=1 while :; do echo "Round $i" echo "Mounting" systemctl start remote-fs.target echo -n "Waiting on mount.nfs processes to complete " while pgrep mount.nfs >/dev/null; do echo -n "." sleep 1 done echo -e "\nNumber of nfs4 mounts: $(grep -c nfs4 /proc/mounts)" echo -e "Unmounting" umount -a -t nfs4 if ! pgrep gssd >/dev/null; then echo "gssd is not running - check for crash" break fi echo "Sleeping 5 seconds" sleep 5 let i=$i+1 done ---8<--- 2) In an AD environment in our lab, I added 1000 test users. On a client machine I have all those users run a script that writes to files on a NetApp SVM and while that script is running I trigger a LIF migration on the filer. That forces all those users to establish new creds with the SVM. That test looks basically like this # for i in `seq 1 1000`; do su - testuser$i -c "echo 'PASSWORD'|kinit"; done # for i in `seq 1 1000`; do su - testuser$i -c "date >/mnt/t/tmp/testuser$i-testfile" & done # for i in `seq 1 1000`; do su - testuser$i -c test.sh & done where test.sh is a simple script that writes the date to a file in a loop: ---8<--- #!/bin/bash filename=/mnt/t/tmp/$(whoami)-testfile for i in $(seq 1 300) do date >$filename sleep 1 done ---8<--- While the test users are running the script I run one of the following commands on the NetApp filer: network interface migrate -vserver VSERVER -lif LIF -destination-node NODE network interface revert -vserver VSERVER -lif LIF -Scott Scott Mayhew (2): gssd: deal with failed thread creation gssd: add timeout for upcall threads nfs.conf | 2 + utils/gssd/gssd.c | 256 +++++++++++++++++++++++----------- utils/gssd/gssd.h | 29 +++- utils/gssd/gssd.man | 31 ++++- utils/gssd/gssd_proc.c | 306 ++++++++++++++++++++++++++++++++++------- 5 files changed, 491 insertions(+), 133 deletions(-) -- 2.30.2