diff options
| author | Vivek Goyal <vgoyal@redhat.com> | 2019-01-16 16:04:15 -0500 |
|---|---|---|
| committer | Eryu Guan <guaneryu@gmail.com> | 2019-01-17 11:15:09 +0800 |
| commit | 23703a8d22dbe293ebcbd4a2faa5a623dff3be56 (patch) | |
| tree | c0d2ab19934926beaa7cbbc2c7a0c71c1bc036a2 /tests/overlay/064.out | |
| parent | be5dedec18d2dbc5125c49c58e43eef49498918c (diff) | |
overlay: File capabilities should not be lost over copy-up
Make sure file capabilities are not lost over copy-up when file is
opened for WRITE but nothing is actually written to it.
Following commit introduced regression where if a lower file with
CAP_SETUID is opened for writing, and capability is cleared over copy up.
bd64e57586d3 ("ovl: During copy up, first copy up metadata and then data")
A later kernel patch will fix it. This test will help avoid introducing
such regressions again.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
Diffstat (limited to 'tests/overlay/064.out')
| -rw-r--r-- | tests/overlay/064.out | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/overlay/064.out b/tests/overlay/064.out new file mode 100644 index 00000000..7ae2244e --- /dev/null +++ b/tests/overlay/064.out @@ -0,0 +1,2 @@ +QA output created by 064 +SCRATCH_MNT/file = cap_setuid+ep |