From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EE9D913C3F3; Tue, 28 May 2024 08:28:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716884885; cv=none; b=N6zeOOcSywXkM0Q1PYcH7aU4ywMv8FStZFRAVKQK9eerFNPDH+8Z7B3abAXykdQOhl9pMXJGGWi+LHGpyUU/E+DUrjo7E7eb/fJf2vLcWAnqkJ6C4zVbjyMI4aaeGuJ9UJsoQIi9Sqa11MeBut8dFmdttXjTYHtJ5D1KxIbtNCw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716884885; c=relaxed/simple; bh=I4rJx3Vi7g8QyIjXX/Wgz8GsjvztY6q4ysfS3GR5qiI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Ys65yQbd6XpNBs8PVTyOJ+CBM1w9SKXEpg2O4SH1vFO9eF1md2OK8WTbJHCLFDpMaKipoX40rpFB6cUvwj2mXjdvqc3mig7dw86VNlt3GHMqSSRu/FsRZdGikymdt/1oDO+vNpQlIpzuYCbUHz9l5fijNhrfYhJyWK2XebIWO0o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=prbu0lei; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="prbu0lei" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=T1FIunXr6SUrbznzUoW3R7DYmUUGSbdYlhleRsosS7w=; b=prbu0leiIBpQYY5tpyT42PKygl hfa7Y2pw4QeYIZ/EEwGxYajHs/B9jVTVzjL06KaDsUdQb+EvH2qsBNEN8A0u3QME3BlU32oQOltQi 2uyG4K9CcQpJYkkz5WaxU25h+BoQnsT0+dU+xvSjZu4/hoDIMvH/2rlAR3It7oJhnHcFV8MpObUcY uKSeEEfDXy3BcX6HUo69J+W0Zn5D1eYtEpAA2o7nxPj0fz9XZKrYJEDZtbjulKhuUlhOtxraKkj09 9kHBs/6ow304OJ+aYk7tpbku90oOYylCKgs4xoaC0bnDTDj61WBSR/SUE3n3iiI0KJxKfN4Bqr1yo Jwu/zX5Q==; Received: from hch by bombadil.infradead.org with local (Exim 4.97.1 #2 (Red Hat Linux)) id 1sBsBc-0000000HTn5-1wEW; Tue, 28 May 2024 08:28:00 +0000 Date: Tue, 28 May 2024 01:28:00 -0700 From: Christoph Hellwig To: Christian Brauner Cc: Christoph Hellwig , Jan Kara , Aleksa Sarai , Alexander Viro , Chuck Lever , Jeff Layton , Amir Goldstein , Alexander Aring , linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2) Message-ID: References: <20240523-exportfs-u64-mount-id-v2-1-f9f959f17eb1@cyphar.com> <20240526.184753-detached.length.shallow.contents-jWkMukeD7VAC@cyphar.com> <20240527133430.ifjo2kksoehtuwrn@quack3> <20240528-wachdienst-weitreichend-42f8121bf764@brauner> Precedence: bulk X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240528-wachdienst-weitreichend-42f8121bf764@brauner> X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Tue, May 28, 2024 at 10:20:21AM +0200, Christian Brauner wrote: > > This would solve all the problems in this proposal as well as all the > > obvious ones it doesn't solve. > > As I've said multiple times on the thread I agree that this is what we > should do next and I would be happy to take patches for this. But > exposing the 64bit mount id doesn't impede or complicate that work. It's > a simple and useful addition that can be done now and doesn't prevent us > from doing the proposed work. I really confuses the user story as we now have not only one but two broken modes for the open by handle ops. We just further go down the rabbit hole of mixing a non-persistent identifiers with a persistent one. > Hell, if you twist my arm I'll even write the patches for this. I'm also happy to help with that despite very limited time, but I'd rather avoid doing the misguided mount ID thing.