[lkml]   [2022]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] vfs: escape hash as well
On Tue, Jun 28, 2022 at 08:30:58AM +0800, Ian Kent wrote:
> From: Siddhesh Poyarekar <>
> When a filesystem is mounted with a name that starts with a #:
> # mount '#name' /mnt/bad -t tmpfs
> this will cause the entry to look like this (leading space added so
> that git does not strip it out):
> #name /mnt/bad tmpfs rw,seclabel,relatime,inode64 0 0
> This breaks getmntent and any code that aims to parse fstab as well as
> /proc/mounts with the same logic since they need to strip leading spaces
> or skip over comment lines, due to which they report incorrect output or
> skip over the line respectively.
> Solve this by translating the hash character into its octal encoding
> equivalent so that applications can decode the name correctly.
> Signed-off-by: Siddhesh Poyarekar <>
> Signed-off-by: Ian Kent <>

ACK; I'll grab that one (in #work.misc - I don't believe it's #fixes

 \ /
  Last update: 2022-06-28 19:58    [W:0.086 / U:0.344 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site