From: Andreas Gruenbacher Subject: Re: [PATCH] Fix d_path for lazy unmounts Date: Wed, 14 Feb 2007 11:39:40 -0800 Message-ID: <200702141139.41465.agruen@suse.de> References: <200702021923.02491.agruen@suse.de> <200702140019.36378.agruen@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, Andrew Morton , Al Viro , linux-fsdevel@vger.kernel.org, Tony Jones , Neil Brown , Christoph Hellwig , Greg Kroah-Hartman , walt To: Linus Torvalds Return-path: Received: from ns2.suse.de ([195.135.220.15]:44819 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751164AbXBNTjp (ORCPT ); Wed, 14 Feb 2007 14:39:45 -0500 In-Reply-To: Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wednesday 14 February 2007 07:37, Linus Torvalds wrote: > We could prepend another '/' (so that you'd have a path that starts with > "//"). That's still a legal path, but it's also somethign that even POSIX > says is valid to mean something else (eg "//ftp/.." or "//socket/.." to > escape into another namespace). This sounds good enough to me. My main point is that users that care should be able to tell the difference. Thanks, Andreas