aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorMiklos Szeredi <[email protected]>2018-10-31 11:15:23 +0000
committerMiklos Szeredi <[email protected]>2018-10-31 11:15:23 +0000
commit5e1275808630ea3b2c97c776f40e475017535f72 (patch)
tree0a7d5c43ac0b662ad2822627a6f2dbc371c21530 /tools/perf/scripts/python/mem-phys-addr.py
parentovl: using posix_acl_xattr_size() to get size instead of posix_acl_to_xattr() (diff)
downloadkernel-5e1275808630ea3b2c97c776f40e475017535f72.tar.gz
kernel-5e1275808630ea3b2c97c776f40e475017535f72.zip
ovl: check whiteout in ovl_create_over_whiteout()
Kaixuxia repors that it's possible to crash overlayfs by removing the whiteout on the upper layer before creating a directory over it. This is a reproducer: mkdir lower upper work merge touch lower/file mount -t overlay overlay -olowerdir=lower,upperdir=upper,workdir=work merge rm merge/file ls -al merge/file rm upper/file ls -al merge/ mkdir merge/file Before commencing with a vfs_rename(..., RENAME_EXCHANGE) verify that the lookup of "upper" is positive and is a whiteout, and return ESTALE otherwise. Reported by: kaixuxia <[email protected]> Signed-off-by: Miklos Szeredi <[email protected]> Fixes: e9be9d5e76e3 ("overlay filesystem") Cc: <[email protected]> # v3.18
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions