diff options
| author | Thomas Weißschuh <linux@weissschuh.net> | 2023-06-07 20:28:48 +0300 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2023-06-07 22:49:55 +0300 |
| commit | 62176420274db5b5127cd7a0083a9aeb461756ee (patch) | |
| tree | 97bae99e6d636fc907d112fb908d193aa4de9d11 /fs/buffer.c | |
| parent | 943211c87427f25bd22e0e63849fb486bb5f87fa (diff) | |
| download | linux-62176420274db5b5127cd7a0083a9aeb461756ee.tar.xz | |
fs: avoid empty option when generating legacy mount string
As each option string fragment is always prepended with a comma it would
happen that the whole string always starts with a comma. This could be
interpreted by filesystem drivers as an empty option and may produce
errors.
For example the NTFS driver from ntfs.ko behaves like this and fails
when mounted via the new API.
Link: https://github.com/util-linux/util-linux/issues/2298
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Fixes: 3e1aeb00e6d1 ("vfs: Implement a filesystem superblock creation/configuration context")
Cc: stable@vger.kernel.org
Message-Id: <20230607-fs-empty-option-v1-1-20c8dbf4671b@weissschuh.net>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/buffer.c')
0 files changed, 0 insertions, 0 deletions