diff options
author | Christian Brauner <[email protected]> | 2024-10-14 16:31:22 +0200 |
---|---|---|
committer | Christian Brauner <[email protected]> | 2024-10-14 16:31:22 +0200 |
commit | 58439f6c48a9dc7a12765a6b37a5c43a542ea90f (patch) | |
tree | 7dc972388902272687e9f4ca69a6298a2d45d917 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 8e929cb546ee42c9a61d24fae60605e9e3192354 (diff) | |
parent | af9199145b1977316b3c752e2124543e320f087f (diff) |
Merge patch series "ovl: file descriptors based layer setup"
Christian Brauner <[email protected]> says:
Currently overlayfs only allows specifying layers through path names.
This is inconvenient for users such as systemd that want to assemble an
overlayfs mount purely based on file descriptors.
When porting overlayfs to the new mount api I already mentioned this.
This enables user to specify both:
fsconfig(fd_overlay, FSCONFIG_SET_FD, "upperdir+", NULL, fd_upper);
fsconfig(fd_overlay, FSCONFIG_SET_FD, "workdir+", NULL, fd_work);
fsconfig(fd_overlay, FSCONFIG_SET_FD, "lowerdir+", NULL, fd_lower1);
fsconfig(fd_overlay, FSCONFIG_SET_FD, "lowerdir+", NULL, fd_lower2);
in addition to:
fsconfig(fd_overlay, FSCONFIG_SET_STRING, "upperdir+", "/upper", 0);
fsconfig(fd_overlay, FSCONFIG_SET_STRING, "workdir+", "/work", 0);
fsconfig(fd_overlay, FSCONFIG_SET_STRING, "lowerdir+", "/lower1", 0);
fsconfig(fd_overlay, FSCONFIG_SET_STRING, "lowerdir+", "/lower2", 0);
The selftest contain an example for this.
* patches from https://lore.kernel.org/r/[email protected]:
selftests: add overlayfs fd mounting selftests
selftests: use shared header
Documentation,ovl: document new file descriptor based layers
ovl: specify layers via file descriptors
fs: add helper to use mount option as path or fd
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions