Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp2827089ybx; Fri, 8 Nov 2019 09:51:57 -0800 (PST) X-Google-Smtp-Source: APXvYqyIepBTZO5WJ2j4WyeZvZYUR6gRP/fUmWJmEn70E7zxwBCNVqlVuPg5cejagQpzl2655r4T X-Received: by 2002:a17:906:6d8a:: with SMTP id h10mr10007493ejt.224.1573235517144; Fri, 08 Nov 2019 09:51:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573235517; cv=none; d=google.com; s=arc-20160816; b=RbEYhGEUJa0ZPgGO995c9tGD7LwyUvzHsNkA4ob2mryJjF887iZxsyK0X1qNvgY2el KYF+BRM4klAb5QaAmEloAxysAVRnGLkXqHSLpLFlEZJWnP2z7kfb8g1FP8XrRs0P8K+a G7XZ4jy3BbsHZoJ+iUWFPj1b+jIY3hn1B/To3KqCN9+tjtgyFcZiIZ+meorYMyW03cKv ALBb9egWh/rR5O5kxRt2rLwGAPqwAznj+nLtF+IgE5fyW15i8MbT2fwk8NNO5i4ZthD5 DGXR7WK9G65tH5adIiIcykPxfm9pjusvlq+84SQgw7Sip4PcHPsvBDDA6Tbr7Cz5zW+m vW4Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=5iXXHrIYPstSTFmX6X3hVwrqscJylG0TybH2nnCT6o4=; b=DXP5xfmzAAgys1Bpfe5WnkDnHSKAk+AfKGH1fmELbe82p6IFbzSEcTeQuuc5BJueqR r4HgeZslXdqG9dRIX5ohtlGNWY1XVHeFfUdWY1VxJAsFqnI6lhOMrWtF+p6bmNhlf5tc q7KYX6DR8kGUABoUbbFWonqvhYOZkcg5aisKN7My5IWYp3iPCLqVmv+jJbqS2QI8a8lf 4w4PG2ogqP6hDolpqssY80zxbTr/yRJlEyPX1oYWqigYQDDAdhL+QJ9oCZbV1MT3QnYR 71brnR2Nt75lI598dPi6+cjEw9S7PSgIkcUS7xGWn2pehRnRp/fIXg2PAhM8rup1GcAP WzLQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id oq2si4189083ejb.402.2019.11.08.09.51.24; Fri, 08 Nov 2019 09:51:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726819AbfKHRvK (ORCPT + 99 others); Fri, 8 Nov 2019 12:51:10 -0500 Received: from fieldses.org ([173.255.197.46]:36434 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726445AbfKHRvK (ORCPT ); Fri, 8 Nov 2019 12:51:10 -0500 Received: by fieldses.org (Postfix, from userid 2815) id D27101C15; Fri, 8 Nov 2019 12:51:09 -0500 (EST) Date: Fri, 8 Nov 2019 12:51:09 -0500 From: "J. Bruce Fields" To: "J. Bruce Fields" Cc: Trond Myklebust , "linux-nfs@vger.kernel.org" Subject: Re: [PATCH v2] nfsd: Fix races between nfsd4_cb_release() and nfsd4_shutdown_callback() Message-ID: <20191108175109.GA758@fieldses.org> References: <20191023214318.9350-1-trond.myklebust@hammerspace.com> <20191025145147.GA16053@pick.fieldses.org> <97f56de86f0aeafb56998023d0561bb4a6233eb8.camel@hammerspace.com> <20191025152119.GC16053@pick.fieldses.org> <20191025153336.GA20283@fieldses.org> <20191029214705.GA29280@fieldses.org> <20191107222712.GB10806@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191107222712.GB10806@fieldses.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Thu, Nov 07, 2019 at 05:27:12PM -0500, J. Bruce Fields wrote: > On Tue, Oct 29, 2019 at 05:47:05PM -0400, J. Bruce Fields wrote: > > On Fri, Oct 25, 2019 at 11:33:36AM -0400, bfields wrote: > > > On Fri, Oct 25, 2019 at 11:21:19AM -0400, J. Bruce Fields wrote: > > > > I thought I was running v2, let me double-check.... > > > > > > Yes, with v2 I'm getting a hang on generic/013. > > > > > > I checked quickly and didn't see anything interesting in the logs, > > > otherwise I haven't done any digging. > > > > Reproduceable just with ./check -nfs generic/013. The last thing I see > > in wireshark is an asynchronous COPY call and reply. Which means it's > > probably trying to do a CB_OFFLOAD. Hm. > > Oh, I think it just needs the following. Applying as follows, with part of the change split out into a separate patch (since that's how I noticed the bug). --b.