summaryrefslogtreecommitdiffstats
path: root/fs/overlayfs/readdir.c
diff options
context:
space:
mode:
authorLinus Torvalds2017-11-17 22:21:58 +0100
committerLinus Torvalds2017-11-17 22:21:58 +0100
commit5a3e0b196bbd63759e9eba836fc7ed16d1f2a1c1 (patch)
tree60407bb01c482726f733d39acd93393a092bf46a /fs/overlayfs/readdir.c
parentMerge branch 'work.cramfs' of git://git.kernel.org/pub/scm/linux/kernel/git/v... (diff)
parentfcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall (diff)
downloadkernel-qcow2-linux-5a3e0b196bbd63759e9eba836fc7ed16d1f2a1c1.tar.gz
kernel-qcow2-linux-5a3e0b196bbd63759e9eba836fc7ed16d1f2a1c1.tar.xz
kernel-qcow2-linux-5a3e0b196bbd63759e9eba836fc7ed16d1f2a1c1.zip
Merge tag 'locks-v4.15-1' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux
Pull file locking update from Jeff Layton: "A couple of fixes for a patch that went into v4.14, and the bug report just came in a few days ago.. It passes my (minimal) testing, and has been in linux-next for a few days now. I also would like to get my address changed in MAINTAINERS to clear that hurdle" * tag 'locks-v4.15-1' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux: fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall fcntl: don't leak fd reference when fixup_compat_flock fails MAINTAINERS: s/jlayton@poochiereds.net/jlayton@kernel.org/
Diffstat (limited to 'fs/overlayfs/readdir.c')
0 files changed, 0 insertions, 0 deletions