summaryrefslogtreecommitdiffstats
path: root/fs/char_dev.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2019-05-01 16:58:24 +0200
committerDavid Howells <dhowells@redhat.com>2019-05-07 17:48:44 +0200
commita2f611a3dc317d8ea1c98ad6c54b911cf7f93193 (patch)
tree3e0852bef6a908c794b88e74dbdb4efad7c8b1d9 /fs/char_dev.c
parentafs: Fix the afs.cell and afs.volume xattr handlers (diff)
downloadlinux-a2f611a3dc317d8ea1c98ad6c54b911cf7f93193.tar.xz
linux-a2f611a3dc317d8ea1c98ad6c54b911cf7f93193.zip
afs: Fix getting the afs.fid xattr
The AFS3 FID is three 32-bit unsigned numbers and is represented as three up-to-8-hex-digit numbers separated by colons to the afs.fid xattr. However, with the advent of support for YFS, the FID is now a 64-bit volume number, a 96-bit vnode/inode number and a 32-bit uniquifier (as before). Whilst the sprintf in afs_xattr_get_fid() has been partially updated (it currently ignores the upper 32 bits of the 96-bit vnode number), the size of the stack-based buffer has not been increased to match, thereby allowing stack corruption to occur. Fix this by increasing the buffer size appropriately and conditionally including the upper part of the vnode number if it is non-zero. The latter requires the lower part to be zero-padded if the upper part is non-zero. Fixes: 3b6492df4153 ("afs: Increase to 64-bit volume ID and 96-bit vnode ID for YFS") Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/char_dev.c')
0 files changed, 0 insertions, 0 deletions