Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp1660281pxy; Fri, 23 Apr 2021 13:39:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy6jOAKoxcbtHY/XmIuuMzGIuyRdoXWVUGqZStA+9dGU20L5e3+HARkccVDIYDjaqKbd/pa X-Received: by 2002:a05:6a00:1651:b029:241:afa4:92b1 with SMTP id m17-20020a056a001651b0290241afa492b1mr5736738pfc.12.1619210374701; Fri, 23 Apr 2021 13:39:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619210374; cv=none; d=google.com; s=arc-20160816; b=ZaRWYAt/QQJWNNxBxT+2v84ERmaFzOMZRCVk9iodWSLjlifgbQ0oH6W60rPlygxyxl lGX2IzSAW07Vg/tTZhWu8odZFYLVN2EeVhjQHn3SidjqNsTCswLsREqkBECbCwUUpfOX LsqDsfQV5zEHRifZbOomUgsVVJECF3wZdn28lWAISTa0zIdE08Kmt0gUaiLxVZW+V+Dv aPyjqGX2BDg6odFo/kHsKUHXzffpdD4+dgmeXqtdMZfxU9yz+pqFdFe98vWn+8mX8hq5 ++nNMEef8Z0pvOLljIbA6HtCXQYBvLrfTp+PT7fwYHbRaA6Goy4uaizEPlPhb805HgAf SGzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:reply-to:message-id:subject:cc:to:from:date; bh=UBiUQ/q4KFmb6pySQGUAJR5QmFFXsDeJ0O+AyRvpCYE=; b=gB3pwM8/kbwUWNhWgheVf4jPWVsVPMKs2h7He1Ng8HYFdsq7qiI99IP7XGobwmmPgj bzbxv/4aRhcYOZkuCaPEe4kek5h8CB87XGjJXIXwzknR7yy3HDzSo5KiNQ6nYZiy65bi hxz+wcuXSB4uZPxjMIhACjhYk1hGqRcv5H0A4Zv+5e6caApK5GuexoQCVuTbuXMvID5G lYq06PRwk+DZ6humYA7fyKGMA8lao2loWhXLEBVOC1bvp1leZPPF/we9C/6dM5UjBglA i5GQ36vvCfNAPL9PFzRiT5Qx94V/kxlhogxFRNCmaVvSLtqREPsDrgAzV/QW/E+yBkm2 kjUA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o11si8143723pls.131.2021.04.23.13.39.11; Fri, 23 Apr 2021 13:39:34 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243932AbhDWUhq (ORCPT + 99 others); Fri, 23 Apr 2021 16:37:46 -0400 Received: from mx2.suse.de ([195.135.220.15]:60420 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232689AbhDWUhl (ORCPT ); Fri, 23 Apr 2021 16:37:41 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 26741B035; Fri, 23 Apr 2021 20:37:04 +0000 (UTC) Date: Fri, 23 Apr 2021 22:37:02 +0200 From: Petr Vorel To: "J . Bruce Fields" Cc: linux-nfs@vger.kernel.org, Steve Dickson , NeilBrown , Chuck Lever , Alexey Kodanev Subject: Re: [RFC PATCH 1/1] mount.nfs: Fix mounting on tmpfs Message-ID: Reply-To: Petr Vorel References: <20210422191803.31511-1-pvorel@suse.cz> <20210422202334.GB25415@fieldses.org> <20210423142329.GB10457@fieldses.org> <20210423181345.GE10457@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210423181345.GE10457@fieldses.org> Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org > On Fri, Apr 23, 2021 at 07:04:41PM +0200, Petr Vorel wrote: > > Hi Bruce, > > > On Fri, Apr 23, 2021 at 04:17:52AM +0200, Petr Vorel wrote: > > > > Hi, > > > > > On Thu, Apr 22, 2021 at 09:18:03PM +0200, Petr Vorel wrote: > > > > > > LTP NFS tests (which use netns) fails on tmpfs since d4066486: > > > > > > mount -t nfs -o proto=tcp,vers=4.2 10.0.0.2:/tmp/ltp.nfs01.nfs-4.2/LTP_nfs01.UF6gRZCy3O/4.2/tcp /tmp/ltp.nfs01.nfs-4.2/LTP_nfs01.UF6gRZCy3O/4.2/0 > > > > > > mount.nfs: mounting 10.0.0.2:/tmp/ltp.nfs01.nfs-4.2/LTP_nfs01.UF6gRZCy3O/4.2/tcp failed, reason given by server: No such file or directory > > > > > We should figure out the reason for the failure. A network trace might > > > > > help. > > > > Anything specific you're looking for? > > > Actually I was thinking of capturing the network traffic, something > > > like: > > > tcpdump -s0 -wtmp.pcap -i > > > then try the mount, then kill tcpdump and look at tmp.pcap. > > I don't see anything suspicious, can you please have a look? > > https://gitlab.com/pevik/tmp/-/raw/master/nfs.v3.pcap > > https://gitlab.com/pevik/tmp/-/raw/master/nfs.v4.pcap > > https://gitlab.com/pevik/tmp/-/raw/master/nfs.v4.1.pcap > > https://gitlab.com/pevik/tmp/-/raw/master/nfs.v4.2.pcap > It might be the "hide" option, that's odd: > > exportfs -v > > /tmp/LTP_nfs01.xkKpqpRikV/4.2/tcp > > (sync,wdelay,hide,no_subtree_check,fsid=7239,sec=sys,rw,secure,no_root_squash,no_all_squash) NOTE: hide is also in v3, which is working. I can provide you even setup. I thought it's related to mount.nfs change (I tested it on openSUSE and Debian, with various kernel versions), but the real cause might be in kernel or elsewhere. Kind regards, Petr > --b.