nfs: get rid of ->set_security()

Browse source

it's always either nfs_set_sb_security() or nfs_clone_sb_security(),
the choice being controlled by mount_info->cloned != NULL.  No need
to add methods, especially when both instances live right next to
the caller and are never accessed anywhere else.

Reviewed-by: David Howells <dhowells@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

...

This commit is contained in:

Al Viro 2019-12-10 07:31:03 -05:00 • committed by Anna Schumaker

parent ba8b614806

commit adf2314fe6

4 changed files with 21 additions and 55 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

fs/nfs/internal.h

View file

1

fs/nfs/namespace.c

View file

3

fs/nfs/nfs4super.c

View file

69

fs/nfs/super.c

View file