diff options
| author | David Howells <dhowells@redhat.com> | 2019-09-26 17:21:18 +0300 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2019-09-26 17:26:55 +0300 |
| commit | a3bc18a48e2e678efe62f1f9989902f9cd19e0ff (patch) | |
| tree | bdcd852bab324000d1f31e3082c51c94760f8207 /crypto/gcm.c | |
| parent | 1f52aa08d12f8d359e71b4bfd73ca9d5d668e4da (diff) | |
| download | linux-a3bc18a48e2e678efe62f1f9989902f9cd19e0ff.tar.xz | |
jffs2: Fix mounting under new mount API
The mounting of jffs2 is broken due to the changes from the new mount API
because it specifies a "source" operation, but then doesn't actually
process it. But because it specified it, it doesn't return -ENOPARAM and
the caller doesn't process it either and the source gets lost.
Fix this by simply removing the source parameter from jffs2 and letting the
VFS deal with it in the default manner.
To test it, enable CONFIG_MTD_MTDRAM and allow the default size and erase
block size parameters, then try and mount the /dev/mtdblock<N> file that
that creates as jffs2. No need to initialise it.
Fixes: ec10a24f10c8 ("vfs: Convert jffs2 to use the new mount API")
Reported-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: David Howells <dhowells@redhat.com>
cc: David Woodhouse <dwmw2@infradead.org>
cc: Richard Weinberger <richard@nod.at>
cc: linux-mtd@lists.infradead.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'crypto/gcm.c')
0 files changed, 0 insertions, 0 deletions