From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Adding subroot information to /proc/mounts, or obtaining that through other means Date: Thu, 21 Jun 2007 12:19:19 -0700 Message-ID: <467ACF37.8050504@zytor.com> References: <467994BD.6000403@zytor.com> <20070620224135.GC6258@gallifrey> <4679AE5E.4050001@zytor.com> <200706212114.25705.hpj@urpla.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Dr. David Alan Gilbert" , Karel Zak , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Hans-Peter Jansen Return-path: In-Reply-To: <200706212114.25705.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org> Sender: util-linux-ng-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Hans-Peter Jansen wrote: >> That's already handled just fine: >> >> bash-3.1$ mkdir /tmp/'Jag =E4r: \ >> en liten mask' >> bash-3.1$ sudo mount -t tmpfs none '/tmp/Jag =E4r: \ >> en liten mask'/ >> bash-3.1$ tail -1 /proc/mounts >> none /tmp/Jag\040=E4r:\040\134\012en\040liten\040mask tmpfs rw 0 0 >> bash-3.1$ >=20 > Hmm, and what about the even sicker case: /tmp/\040, parse as /tmp/\\= 040? > Do userspace cope with this? Look at the example above, it contains a backslash already. It's escaped as \134. "Does userspace cope with this" is of course an impossible question to answer, since userspace is in theory unbounded. However, if it doesn't= , it is broken and needs to be fixed. -hpa