original_kernel/fs/afs
David Howells f8de483e74 afs: Properly reset afs_vnode (inode) fields
When an AFS inode is allocated by afs_alloc_inode(), the allocated
afs_vnode struct isn't necessarily reset from the last time it was used as
an inode because the slab constructor is only invoked once when the memory
is obtained from the page allocator.

This means that information can leak from one inode to the next because
we're not calling kmem_cache_zalloc().  Some of the information isn't
reset, in particular the permit cache pointer.

Bring the clearances up to date.

Signed-off-by: David Howells <dhowells@redhat.com>
Tested-by: Marc Dionne <marc.dionne@auristor.com>
2017-12-01 11:51:24 +00:00
..
Kconfig
Makefile
addr_list.c
afs.h
afs_cm.h
afs_fs.h
afs_vl.h
cache.c
callback.c
cell.c afs: cell: Remove unnecessary code in afs_lookup_cell 2017-11-24 13:55:45 +00:00
cmservice.c
dir.c afs: remove redundant assignment of dvnode to itself 2017-11-24 13:55:46 +00:00
file.c
flock.c afs: Fix file locking 2017-11-17 10:06:13 +00:00
fsclient.c
inode.c
internal.h afs: Properly reset afs_vnode (inode) fields 2017-12-01 11:51:24 +00:00
main.c
misc.c
mntpt.c
netdevices.c
proc.c
rotate.c afs: Fix file locking 2017-11-17 10:06:13 +00:00
rxrpc.c
security.c afs: Fix permit refcounting 2017-12-01 11:40:43 +00:00
server.c
server_list.c afs: Fix file locking 2017-11-17 10:06:13 +00:00
super.c afs: Properly reset afs_vnode (inode) fields 2017-12-01 11:51:24 +00:00
vlclient.c
volume.c
write.c afs: Make afs_write_begin() avoid writing to a page that's being stored 2017-11-24 10:56:51 +00:00
xattr.c