From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-nfs-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 36142C433EF
	for <linux-nfs@archiver.kernel.org>; Tue, 29 Mar 2022 15:11:47 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S234378AbiC2PN1 (ORCPT <rfc822;linux-nfs@archiver.kernel.org>);
        Tue, 29 Mar 2022 11:13:27 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46716 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S238347AbiC2PNZ (ORCPT
        <rfc822;linux-nfs@vger.kernel.org>); Tue, 29 Mar 2022 11:13:25 -0400
Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1982E22C8E8
        for <linux-nfs@vger.kernel.org>; Tue, 29 Mar 2022 08:11:42 -0700 (PDT)
Received: by fieldses.org (Postfix, from userid 2815)
        id BC605BD6; Tue, 29 Mar 2022 11:11:41 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org BC605BD6
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org;
        s=default; t=1648566701;
        bh=o+Rp/6vqThiRAONR1N9RGjikcnzSGysZQHo/LAlC8LA=;
        h=Date:To:Cc:Subject:References:In-Reply-To:From:From;
        b=rKzzS0YnouHtkocFoWWOyWRStXmFY4eWnlnbEkivQbFsiKCMBFmODr3IvuSFB/8Ka
         l+gzMBNRaJAjUrKLYn2kRdmKIZ8393ybV+VOOQbD8h3DvlcONlW6FdVDLaJAOnOLEm
         Y1vDeA46b94SRLz9biL7Bz2U2Qft30qAxAkb6654=
Date:   Tue, 29 Mar 2022 11:11:41 -0400
To:     Chuck Lever III <chuck.lever@oracle.com>
Cc:     Neil Brown <neilb@suse.de>,
        Benjamin Coddington <bcodding@redhat.com>,
        Steve Dickson <SteveD@RedHat.com>,
        Trond Myklebust <trondmy@hammerspace.com>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH/RFC] NFSv4: ensure different netns do not share
 cl_owner_id
Message-ID: <20220329151141.GA29634@fieldses.org>
References: <164816787898.6096.12819715693501838662@noble.neil.brown.name>
 <CC04FF50-B936-456D-8BF0-4BF04647B4BC@oracle.com>
 <164844195133.6096.11388357137493699567@noble.neil.brown.name>
 <A526C0BA-D123-4A32-BB85-E82D5494043B@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A526C0BA-D123-4A32-BB85-E82D5494043B@oracle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Precedence: bulk
List-ID: <linux-nfs.vger.kernel.org>
X-Mailing-List: linux-nfs@vger.kernel.org

On Mon, Mar 28, 2022 at 02:08:31PM +0000, Chuck Lever III wrote:
> Note also that the protocol allows a CLID_INUSE response to return
> the IP address of the conflicting client, but NFSD doesn't do that,
> I guess as a security measure.

The information disclosure sounds mild and not too surprising--mountd
already hands out information about v2/v3 clients (used by "showmount").

Chances are we just didn't get around to it.  If it'd help debug this
kind of problem, I think it'd be worth it.

--b.