From owner-freebsd-fs@freebsd.org Sat Dec 12 01:47:04 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E97FE47AEC7 for ; Sat, 12 Dec 2020 01:47:04 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ct9WC6p3fz3l4l for ; Sat, 12 Dec 2020 01:47:03 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: by mail-lf1-x133.google.com with SMTP id a9so16141039lfh.2 for ; Fri, 11 Dec 2020 17:47:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MaFewCBAhUEwOBJ+It7wBNoExnse7RFtKcKq4TnYzNw=; b=OxnQp7w7/d8sTIrFYHEr9HtACgnmJ/BLm4UHX009IAxv1Z/KAR48F5xxN+n336twBa YhHp9hWf/6hF5B08QgYj1K0lzItvn7QMGVkGBgEq4eQIkx3hCQDjdxofkW4J0P9wjNOg FvjV6lqPfn9gr1MnMzJ5eQ+SR5OVV9ruGzYkiTJqYDC1nN1X1ZxudFiNbPx46oMz0J9Q w66mn58VLlwojOdJ7yxbeyEj9rklj/czQfhshh890ZZ5IzukHN3JqleYPCQJAefHH5D7 hKpXdZGn9bRibfvuuoUIt/0cRlf4d2xvOk0g57mJ/VIaGBwCtx/Rl5jtXCWQiuykSwOr lROg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MaFewCBAhUEwOBJ+It7wBNoExnse7RFtKcKq4TnYzNw=; b=U3hrh56V25yxiCd9lwO+0F0TViBxKrLvMaF5aBvAuTu0t4tDzx+0L92Q/hDutux0Ba hUYURD1Ge3cwWiptupJZ8K3WooviT7KZ7ZZtoALKQCdpKa+rcrGz8vA5z7OCLkHnyClm sesQdmTYcuzdpvsf8VGcHODdXk//dS3E2B02om6bU0asbBnwJcymfrWcALOCPDOAEnuT FgnJNGWy2ndONtcjzqiS9sjyFCffyw3Jy2w1utnKLt1vlzgZ3HRH0w+NRN/kb8jTXd6H ypbineEViBiTfT0rCdBRtot/fng3vG+QwF5Zrnf7SCe9CKZB7eZ0Equh2h0QSMoYb2FI +WqA== X-Gm-Message-State: AOAM532sHQFgin5l8GW+uSa2+2qLp7kExLawuwv0/Xgtdjiso66xqKiK cAjAzC+u7emq0aM9Ob5NllBTYbK+eBK+g/+V1Kc= X-Google-Smtp-Source: ABdhPJwAoEjucziKRKlgBELdr1eI2R3032kRhVeslvrHY1jIbFjlrfPdPxqLFNyRvZBhWV7Q5iskwRCkgatdEEwPbnw= X-Received: by 2002:a05:651c:1341:: with SMTP id j1mr5128621ljb.216.1607737622128; Fri, 11 Dec 2020 17:47:02 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: J David Date: Fri, 11 Dec 2020 20:46:51 -0500 Message-ID: Subject: Re: Major issues with nfsv4 To: Rick Macklem Cc: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Ct9WC6p3fz3l4l X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=OxnQp7w7; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of jdavidlists@gmail.com designates 2a00:1450:4864:20::133 as permitted sender) smtp.mailfrom=jdavidlists@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::133:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::133:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::133:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Dec 2020 01:47:05 -0000 On Fri, Dec 11, 2020 at 6:28 PM Rick Macklem wrote: > I am afraid I know nothing about nullfs and jails. I suspect it will be > something related to when file descriptors in the NFS client mount > get closed. What does NFSv4 do differently than NFSv3 that might upset a low-level consumer like nullfs? > Well, NFSv3 is not going away any time soon, so if you don't need > any of the additional features it offers... If we did not want the additional features, we definitely would not be attempting this. > a user would have to run their own custom hacked > userland NFS client. Although doable, I have never heard of it being done. Alex beat me to libnfs. What about this as a stopgap measure? > How explosive would adding SO_REUSEADDR to the NFS client be? It's > not a full solution, but it would handle the TIME_WAIT side of the > issue. The kernel NFS networking code is confusing to me. I can't even figure out where/how NFSv4 binds a client socket to know if it's possible. (Pretty sure the code in sys/nfs/krpc_subr.c is not it.) Thanks!