diff options
| author | Vivek Goyal <[email protected]> | 2019-01-30 14:01:57 -0500 |
|---|---|---|
| committer | Miklos Szeredi <[email protected]> | 2019-02-13 11:14:46 +0100 |
| commit | 993a0b2aec52754f0897b1dab4c453be8217cae5 (patch) | |
| tree | b2e1d4fbcb37495bea2aaa9ecf3ba8562382f208 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 5f32879ea35523b9842bdbdc0065e13635caada2 (diff) | |
ovl: Do not lose security.capability xattr over metadata file copy-up
If a file has been copied up metadata only, and later data is copied up,
upper loses any security.capability xattr it has (underlying filesystem
clears it as upon file write).
From a user's point of view, this is just a file copy-up and that should
not result in losing security.capability xattr. Hence, before data copy
up, save security.capability xattr (if any) and restore it on upper after
data copy up is complete.
Signed-off-by: Vivek Goyal <[email protected]>
Reviewed-by: Amir Goldstein <[email protected]>
Fixes: 0c2888749363 ("ovl: A new xattr OVL_XATTR_METACOPY for file on upper")
Cc: <[email protected]> # v4.19+
Signed-off-by: Miklos Szeredi <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions