[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] [xen staging] tools/dm_restrict: Ask QEMU to chroot
commit 7414750be1fed21687a0a28f67cc2397ebb0d0ba Author: George Dunlap <george.dunlap@xxxxxxxxxx> AuthorDate: Tue Nov 6 15:41:23 2018 +0000 Commit: George Dunlap <george.dunlap@xxxxxxxxxx> CommitDate: Tue Nov 6 15:41:23 2018 +0000 tools/dm_restrict: Ask QEMU to chroot When dm_restrict is enabled, ask QEMU to chroot into an empty directory. * Create $XEN_RUN_DIR/qemu-root-<domid> (deleting the old one if it's there) * Pass the -chroot option to QEMU Rather than running `rm -rf` on the directory before creating it (since there is no library function to do this), simply rmdir the directory, relying on the fact that the previous QEMU instance, if properly restricted, shouldn't have been able to write anything anyway. Suggested-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx> Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> --- Changes since v4: - Minor change to comment - Update stale directory name in commit message Changes since v2: - Style fixes - Testing moved to a different patch CC: Ian Jackson <ian.jackson@xxxxxxxxxx> CC: Wei Liu <wei.liu2@xxxxxxxxxx> CC: Anthony Perard <anthony.perard@xxxxxxxxxx> --- docs/designs/qemu-deprivilege.md | 12 ++++++------ tools/libxl/libxl_dm.c | 41 +++++++++++++++++++++++++++++++++++++++- 2 files changed, 46 insertions(+), 7 deletions(-) diff --git a/docs/designs/qemu-deprivilege.md b/docs/designs/qemu-deprivilege.md index 37a4d675fe..82b0e15d81 100644 --- a/docs/designs/qemu-deprivilege.md +++ b/docs/designs/qemu-deprivilege.md @@ -59,12 +59,6 @@ source tree.) '''Testing status''': Tested -# Restrictions / improvements still to do - -This lists potential restrictions still to do. It is meant to be -listed in order of ease of implementation, with low-hanging fruit -first. - ## Chroot '''Description''': Qemu runs in its own chroot, such that even if it @@ -82,6 +76,12 @@ Then adds the following to the qemu command-line: '''Tested''': Not tested +## Restrictions / improvements still to do + +This lists potential restrictions still to do. It is meant to be +listed in order of ease of implementation, with low-hanging fruit +first. + ## Namespaces for unused functionality (Linux only) '''Description''': QEMU doesn't use the functionality associated with diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 26eb16af34..bb3e3a625c 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -1410,9 +1410,48 @@ static int libxl__build_device_model_args_new(libxl__gc *gc, } } - if (libxl_defbool_val(b_info->dm_restrict)) + if (libxl_defbool_val(b_info->dm_restrict)) { + char *chroot_dir = GCSPRINTF("%s/qemu-root-%d", + libxl__run_dir_path(), guest_domid); + int r; + flexarray_append(dm_args, "-xen-domid-restrict"); + /* + * Run QEMU in a chroot at XEN_RUN_DIR/qemu-root-<domid> + * + * There is no library function to do the equivalent of `rm + * -rf`. However deprivileged QEMU in theory shouldn't be + * able to write any files, as the chroot would be owned by + * root, but it would be running as an unprivileged process. + * So in theory, old chroots should always be empty. + * + * rmdir the directory before attempting to create + * it; if it returns anything other than ENOENT, fail domain + * creation. + */ + r = rmdir(chroot_dir); + if (r != 0 && errno != ENOENT) { + LOGED(ERROR, guest_domid, + "failed to remove existing chroot dir %s", chroot_dir); + return ERROR_FAIL; + } + + for (;;) { + r = mkdir(chroot_dir, 0000); + if (!r) + break; + if (errno == EINTR) continue; + LOGED(ERROR, guest_domid, + "failed to create chroot dir %s", chroot_dir); + return ERROR_FAIL; + } + + /* Add "-chroot [dir]" to command-line */ + flexarray_append(dm_args, "-chroot"); + flexarray_append(dm_args, chroot_dir); + } + if (state->saved_state) { /* This file descriptor is meant to be used by QEMU */ *dm_state_fd = open(state->saved_state, O_RDONLY); -- generated by git-patchbot for /home/xen/git/xen.git#staging _______________________________________________ Xen-changelog mailing list Xen-changelog@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/xen-changelog
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |