From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="UGntqgn6" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 296B91738 for ; Wed, 13 Dec 2023 07:32:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702481553; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+hdM+h7N6TwHGhwIbks4CvwZuKV0xOWmxmNCull4QN4=; b=UGntqgn6aHLco/6A4iUdqPuSLwkKM1u0yC+VLDS9nluMZ94m+L/H5LfZYNlA3S7Ip1hbzG /RF3MhqIXYzKoB8fG1qwWo33ReUJkUkrwqDehDSa57aLlxKcU0MKLbAY1b2v26KolYCOAe D1g3K0Da8cZmMBC0vSv0SYCvRn/PG4A= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-418-Oq2jS38dPZ6RKRmzjwJH1A-1; Wed, 13 Dec 2023 10:32:30 -0500 X-MC-Unique: Oq2jS38dPZ6RKRmzjwJH1A-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 232C088D01D; Wed, 13 Dec 2023 15:32:28 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.2]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4EA702026D66; Wed, 13 Dec 2023 15:32:25 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <3bf4a5126f84b56a28dbc5e8e643b24945578bbd.camel@kernel.org> References: <3bf4a5126f84b56a28dbc5e8e643b24945578bbd.camel@kernel.org> <20231207212206.1379128-1-dhowells@redhat.com> <20231207212206.1379128-5-dhowells@redhat.com> To: Jeff Layton Cc: dhowells@redhat.com, Steve French , Matthew Wilcox , Marc Dionne , Paulo Alcantara , Shyam Prasad N , Tom Talpey , Dominique Martinet , Eric Van Hensbergen , Ilya Dryomov , Christian Brauner , linux-cachefs@redhat.com, linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org, ceph-devel@vger.kernel.org, v9fs@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 04/59] netfs, fscache: Move /proc/fs/fscache to /proc/fs/netfs and put in a symlink Precedence: bulk X-Mailing-List: linux-nfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <432337.1702481544.1@warthog.procyon.org.uk> Date: Wed, 13 Dec 2023 15:32:24 +0000 Message-ID: <432338.1702481544@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.4 Jeff Layton wrote: > > 1. Are there known userland tools that rely on this path? I suppose > this is harmless either way though, and /proc is supposedly part > of the ABI. I know various people have sent copies of the file in case of crashes, so it feels like it should still be accessible by the old path. David