Al Viro 0f89589a8c Pass consistent param->type to fs_parse()
As it is, vfs_parse_fs_string() makes "foo" and "foo=" indistinguishable;
both get fs_value_is_string for ->type and NULL for ->string.  To make
it even more unpleasant, that combination is impossible to produce with
fsconfig().

Much saner rules would be
        "foo"           => fs_value_is_flag, NULL
	"foo="          => fs_value_is_string, ""
	"foo=bar"       => fs_value_is_string, "bar"
All cases are distinguishable, all results are expressable by fsconfig(),
->has_value checks are much simpler that way (to the point of the field
being useless) and quite a few regressions go away (gfs2 has no business
accepting -o nodebug=, for example).

Partially based upon patches from Miklos.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2020-02-07 00:10:29 -05:00
..
2019-09-27 15:10:34 -07:00
2020-01-03 12:20:21 -08:00
2019-09-19 09:42:37 -07:00
2019-12-09 10:36:44 -08:00
2019-07-12 17:37:53 -07:00
2019-12-11 12:25:32 -08:00
2019-11-11 09:21:59 -05:00
\n
2019-11-30 11:16:07 -08:00
2019-12-05 13:20:11 -08:00
2019-09-19 09:42:37 -07:00
2019-09-19 09:42:37 -07:00
2019-12-14 11:13:54 -08:00
2019-09-19 09:42:37 -07:00
2019-12-09 10:36:44 -08:00
2019-12-01 14:00:59 -08:00
2019-12-02 14:46:22 -08:00
2019-11-30 10:44:49 -08:00
2019-08-07 21:51:47 -04:00
2020-01-02 16:15:33 -08:00
2019-12-02 14:46:22 -08:00
2019-10-14 15:04:01 -07:00