[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220628130348.i5ckfdnyzjtoqgb3@wittgenstein>
Date: Tue, 28 Jun 2022 15:03:48 +0200
From: Christian Brauner <brauner@...nel.org>
To: Ian Kent <raven@...maw.net>
Cc: Al Viro <viro@...IV.linux.org.uk>,
Siddhesh Poyarekar <siddhesh@...plt.org>,
David Howells <dhowells@...hat.com>,
Miklos Szeredi <miklos@...redi.hu>,
Carlos Maiolino <cmaiolino@...hat.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] vfs: parse: deal with zero length string value
On Fri, Jun 17, 2022 at 01:09:03PM +0800, Ian Kent wrote:
> Parsing an fs string that has zero length should result in the parameter
> being set to NULL so that downstream processing handles it correctly.
> For example, the proc mount table processing should print "(none)" in
> this case to preserve mount record field count, but if the value points
> to the NULL string this doesn't happen.
>
> Signed-off-by: Ian Kent <raven@...maw.net>
> ---
Makes sense. Though I feel this is might be one of those instances where
we detect that some code isn't prepared for param.string to be NULL at
some point...
Reviewed-by: Christian Brauner (Microsoft) <brauner@...nel.org>
Powered by blists - more mailing lists