diff options
| author | David Howells <dhowells@redhat.com> | 2018-09-11 22:20:53 +0100 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2018-09-11 22:20:53 +0100 |
| commit | 307c6e5241b4b44076c016bc64d1748b93d1792b (patch) | |
| tree | 6b60bd39e494ea09efdc54e57c4cad7dc80760ce /drivers/dax | |
| parent | 11da3a7f84f19c26da6f86af878298694ede0804 (diff) | |
| download | linux-next-307c6e5241b4b44076c016bc64d1748b93d1792b.tar.gz | |
vfs: Require specification of size of mount data for internal mounts
Require specification of the size of the mount data passed to the VFS
mounting functions by internal mounts. The problem is that the legacy
handling for the upcoming mount-context patches has to copy an entire page
as that's how big the buffer is defined as being, but some of the internal
calls pass in a short bit of stack space, with the result that the stack
guard page may get hit.
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'drivers/dax')
| -rw-r--r-- | drivers/dax/super.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/dax/super.c b/drivers/dax/super.c index 6e928f37d084..bc65ca34ec4b 100644 --- a/drivers/dax/super.c +++ b/drivers/dax/super.c @@ -418,7 +418,7 @@ static const struct super_operations dax_sops = { }; static struct dentry *dax_mount(struct file_system_type *fs_type, - int flags, const char *dev_name, void *data) + int flags, const char *dev_name, void *data, size_t data_size) { return mount_pseudo(fs_type, "dax:", &dax_sops, NULL, DAXFS_MAGIC); } |