Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp741901pxj; Thu, 27 May 2021 10:32:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw+QWMQySiBYl6zoQKxcWuT66cG8qontvSWxZLSgYij7tJ8cF6K9LMBqTG8F0+v4lg97Sa/ X-Received: by 2002:a5e:9515:: with SMTP id r21mr3743453ioj.19.1622136757968; Thu, 27 May 2021 10:32:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622136757; cv=none; d=google.com; s=arc-20160816; b=hmjXo9xvujMRg8dNuYAPafAfckCwzUJeoqyp984pNVjm8rLF90cgMq5keMJAj+GFs8 jGKDCCEhuOhtf70ifG/x7u789eqisc8F20suZdiGpilXWUYio0KG+0/vLXy/XK8+lXF9 H5vjkYNSj/xTi8OphkbU/INWPq5/6W7n0pHEE7thjoFqrKG4mfKw9Sybk4IL3vfJDcN8 IX1CkIvNhWXQjpfHGHbwjDHNqTEQwljH7pH9qXZSqbayKXtqP1m2pGe4Sz3BHn/um+nU to7HQCiOBe87SonjrjxVsXm1cILkP5ezzuJtRupH4o2vCx+E55X4v0Kggipphd4D37bW I4oQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:references:to :from:subject:dkim-signature; bh=cNBropPhQuRfOFrUpZKcbDIjah61wJb8ro7FWpiaGbY=; b=DZsHuWzWbiGj6ij0bqtlC0T2vnW7QhFoJplOgo4o+VqsChWgo2tC/NpcALgoU0bZNq 8Y8QhTelMpcCFcy9gTpD0oDffuxiNtRjGhEA0Ks7CrGfI5axMfFS7HOYxbMw8ikEx6I4 UtjvXUnZOQxqODaIVC4IMJgrMvqTUDE++nZgvZQlAHuYegeGEzDDaHH7J+VhuT9VGkJ2 nxaYldobl2eNm4inEsHwowSecXzFI+se09avyyujHClUi8HLPQbAqhp2DzuTeSgoGSGH 9TVmZgT9l3qI9fgxPpm3mV/78YvGWbDBlgn+lqvCvYeQl9CtuHZtT7tYOEZkV0VkIVHQ 2LoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PMSNCIjs; 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 w135si3177328jaw.24.2021.05.27.10.32.15; Thu, 27 May 2021 10:32:37 -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=PMSNCIjs; 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 S235395AbhE0Pf3 (ORCPT + 99 others); Thu, 27 May 2021 11:35:29 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:20837 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236083AbhE0Pf3 (ORCPT ); Thu, 27 May 2021 11:35:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1622129635; 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=cNBropPhQuRfOFrUpZKcbDIjah61wJb8ro7FWpiaGbY=; b=PMSNCIjs/An8n1UetscK/nsatJ8MVlAR1g4+I4/6vyab5mVq5MnB77owDGInn+vuWVixNF QkpaeuB07y6jUtKXFhk6n/Zsn95MZrzkBjsasenFfYufOx5b6ztzH8GsL2DbPHhHvY8UDB WgN05dIUdDoIb+45N3jN0H6TJhKUTl4= 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-385-DERMI5MZPKuVkLSs7E7rmw-1; Thu, 27 May 2021 11:33:54 -0400 X-MC-Unique: DERMI5MZPKuVkLSs7E7rmw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3DBB3801AEB for ; Thu, 27 May 2021 15:33:53 +0000 (UTC) Received: from madhat.boston.devel.redhat.com (ovpn-112-214.phx2.redhat.com [10.3.112.214]) by smtp.corp.redhat.com (Postfix) with ESMTP id EF52718B15; Thu, 27 May 2021 15:33:52 +0000 (UTC) Subject: Re: [nfs-utils RFC PATCH 2/2] gssd: add timeout for upcall threads From: Steve Dickson To: Scott Mayhew , linux-nfs@vger.kernel.org References: <20210525180033.200404-1-smayhew@redhat.com> <20210525180033.200404-3-smayhew@redhat.com> <490b45eb-0142-24de-e05f-79751891ddf9@RedHat.com> Message-ID: <64b6f93a-e81c-fd8a-8db5-44e69004294d@RedHat.com> Date: Thu, 27 May 2021 11:36:49 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <490b45eb-0142-24de-e05f-79751891ddf9@RedHat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hey! Off-list... On 5/26/21 1:08 PM, Steve Dickson wrote: >> + free(tinfo); >> + return ret; >> + } >> + printerr(1, "created thread id 0x%lx\n", th); > This will be removed... It turns out this tid is useful since the tid is used in the do_downcall() db statement. In general I've try to always used the function name in the db statement so it is know where it is. So maybe something like this: pthread_t tid = pthread_self(); printerr(2, "start_upcall_thread(0x%lx): created thread id 0x%lx\n", tid, th); steved. P.S. After your final version, I'm going to follow up with a debug clean up patch... So I can take care of it there... if you like.