From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f194.google.com ([209.85.192.194]:46696 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732994AbeGLChK (ORCPT ); Wed, 11 Jul 2018 22:37:10 -0400 Received: by mail-pf0-f194.google.com with SMTP id l123-v6so19609556pfl.13 for ; Wed, 11 Jul 2018 19:29:56 -0700 (PDT) Date: Thu, 12 Jul 2018 10:29:50 +0800 From: Yecheng Fu To: Matthew Wilcox , Alexander Viro Cc: linux-fsdevel@vger.kernel.org, Karel Zak Subject: Re: [PATCH v2] vfs: use "none" if mount source is empty string Message-ID: <20180712022848.GA89138@jupiter.local> References: <1524109641-45617-1-git-send-email-cofyc.jackson@gmail.com> <20180419113256.GC5556@bombadil.infradead.org> <20180515051758.GA10231@jupiter.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180515051758.GA10231@jupiter.local> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, May 15, 2018 at 01:18:00PM +0800, Yecheng Fu wrote: > On Thu, Apr 19, 2018 at 04:32:56AM -0700, Matthew Wilcox wrote: > > On Thu, Apr 19, 2018 at 11:47:21AM +0800, Yecheng Fu wrote: > > > `libmount` from util-linux and many softwares in userspace (e.g. > > > kubelet) did not expect empty string as mount source: > > > > > > ``` > > > $ mount -t tmpfs "" /mnt/tmpfs > > > $ findmnt /mnt/tmpfs > > > findmnt: /proc/self/mountinfo: parse error at line 51 > > > $ cat /proc/self/mountinfo | grep -P '\/mnt\/tmpfs' > > > 74 25 0:59 / /mnt/tmpfs rw,relatime shared:38 - tmpfs rw > > > $ cat /proc/self/mounts | grep -P '\/mnt\/tmpfs' > > > /mnt/tmpfs tmpfs rw,relatime 0 0 > > > ``` > > > > > > `source` field in mounts/mountinfo is empty, which breaks a lot of > > > mounts/mountinfo parsers. > > > > > > This fixes issues in parsing when user uses empty string as mount > > > source. > > > > > > Cc: Karel Zak > > > Signed-off-by: Yecheng Fu > > > > Reviewed-by: Matthew Wilcox > > hi, I'm a newbie here. Will this be merged or is there still something I > need to do? > > I had submitted a patch to [util-linux](https://github.com/karelzak/util-linux/pull/619). Karel prefer kernel side bugfix than rewrite all the sscanf() stuff and I agree. Kernel side bugfix also fixes all parsers too. > > -- > Yecheng Fu hi, didn't receive any updates for months, sorry to ping again in case someone missed it. Karel patched util-linux to work around this issue now [^1], but I hope this can be fixed on kernel side too to improve compatibility. [^1]: https://github.com/karelzak/util-linux/commit/18a52a5094f820b5da013daf5972eb8e65be9680 -- Yecheng Fu