Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3972542pxk; Tue, 22 Sep 2020 07:23:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyho7o+KhSPKml3e44wNE0lmLzHbUKeNZg92IRmfFQ+BRLobaZ65kWJzCqc3glwEclxKw1i X-Received: by 2002:a17:906:7248:: with SMTP id n8mr5155092ejk.160.1600784579837; Tue, 22 Sep 2020 07:22:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600784579; cv=none; d=google.com; s=arc-20160816; b=DiT9kXFlZU2re+7H7567COwm/P3fkGWBzbKN8WCAiMTtTCwJAaZs1HeMvSTaW4IJd/ JeoJd2XeXSZx4wMjhytVCSna1wkWOIxvh4kt7GbboFJICyr+c7gi+iTXKQHRIOcPTiEJ 9QOqHiZ81llLQ89BVN/mMHNUO//WAK/EJRpKr1voPAFdrLPFPwz1SOTVGxpM1nxB9N2/ 1CmeTKk3U9n6n8eg2xbGrv7Po4efq4bOJT6JqMNjmK4CD3DTWpWG8LWB8iBWMgyK2hKa zSHwgPx4KYENdV67ne0eytvZv5LPkW2TN31ffrWqiPWFFweNAsEbaxkr8658+kHVPjax cvcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=nsea8EcN/QQ00P2hjXg098n3GKxc7bMiKmiAIyVKRXE=; b=RfbxxQZoTOENs1+uWF3FyAoctnoKajKwTnZLTcVKEBBN7KLaRjiBW/1Wf0TBgJte8X Z6cTqg82VLqO7v2Uwjge3VHt6FpILxGSkxox48mOu8EgCHhuQ4lzhbKkpvYkd60U+ET9 pdVuEAIWyBPPgjQnCSt91Spr7KCRG/S6twf6SPH1S3jxyVI4Xv5iVYMBIP38PIEOhzTV TyfH2Ed0L3Co0slmQUH/cmptLifSWZ5GTYKc2wNIJOmGwiL6vM5Rt/cBCFIWpTnQcg7Y r6FjB8oDDB7LIXHnBz4N17g3blTgnmjDhEMS3EtZxTh6KDfOvGdWQ2UIsT74T/Rq5PSa 2bjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=XAwyqSuc; 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 i24si11298935edb.493.2020.09.22.07.22.34; Tue, 22 Sep 2020 07:22:59 -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=XAwyqSuc; 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 S1726494AbgIVOWX (ORCPT + 99 others); Tue, 22 Sep 2020 10:22:23 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:50717 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726473AbgIVOWX (ORCPT ); Tue, 22 Sep 2020 10:22:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600784542; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nsea8EcN/QQ00P2hjXg098n3GKxc7bMiKmiAIyVKRXE=; b=XAwyqSucQlWiUtB5IHi+ckNNKEINRDzIOP23sYH1k8ySD1pdxAlVuPFBtZeBRg1XZnKhd9 oRwscr4iH27RSVN4/NlsSqy0LT0ee+sIWF8K/ohvjv/K4goL0fdH1GY+std9WtGT0e+MjI RnhNqgKRt0dTvUPAH8Vey38IVH0pMJc= 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-235-FScPb0AcOaCNL_GIMq-3cw-1; Tue, 22 Sep 2020 10:22:20 -0400 X-MC-Unique: FScPb0AcOaCNL_GIMq-3cw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D68DC188C153; Tue, 22 Sep 2020 14:22:18 +0000 (UTC) Received: from [172.16.176.1] (ovpn-64-66.rdu2.redhat.com [10.10.64.66]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7AF9719C4F; Tue, 22 Sep 2020 14:22:18 +0000 (UTC) From: "Benjamin Coddington" To: "Anna Schumaker" Cc: "Trond Myklebust" , "Linux NFS Mailing List" Subject: Re: [PATCH 1/3] NFSv4: Fix a livelock when CLOSE pre-emptively bumps state sequence Date: Tue, 22 Sep 2020 10:22:17 -0400 Message-ID: <8DB79D4D-6986-4114-B031-43157089C2B5@redhat.com> In-Reply-To: References: <5a7f6bbf4cf2038634a572f42ad80e95a8d0ae9c.1600686204.git.bcodding@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On 22 Sep 2020, at 10:03, Anna Schumaker wrote: > Hi Ben, > > Once I apply this patch I have trouble with generic/478 doing lock reclaim: > > [ 937.460505] run fstests generic/478 at 2020-09-22 09:59:14 > [ 937.607990] NFS: __nfs4_reclaim_open_state: Lock reclaim failed! > > And the test just hangs until I kill it. > > Just thought you should know! Yes, thanks! I'm not seeing that.. I've tested these based on v5.8.4, I'll rebase and check again. I see a wirecap of generic/478 is only 515K on my system, would you be willing to share a capture of your test failing? Ben