Commit 4d0c5ba (vfs: do get_write_access() on upper layer of overlayfs) that was merged for kernel v4.8 changes the behavior of execve+truncate in a subtle way. When file is executed from lower and then truncated, the truncation is allowed, becasue it only affects the size of the copied up file and does not affect the VM mapping of the executed lower file. Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> --- tests/overlay/013 | 1 - tests/overlay/013.out | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/tests/overlay/013 b/tests/overlay/013 index e92eeec..e99e10a 100755 --- a/tests/overlay/013 +++ b/tests/overlay/013 @@ -69,6 +69,5 @@ $SCRATCH_MNT/test_lower $SCRATCH_MNT/test_upper # success, all done -echo "Silence is golden" status=0 exit diff --git a/tests/overlay/013.out b/tests/overlay/013.out index 3e66423..b2c7cc7 100644 --- a/tests/overlay/013.out +++ b/tests/overlay/013.out @@ -1,2 +1,2 @@ QA output created by 013 -Silence is golden +truncate(test_lower) should have failed -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
