[systemd-bugs] [Bug 88973] New: systemd-nspawn: No proper error handling when pointing --bind to non-existent directory

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 4 14:24:26 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88973

            Bug ID: 88973
           Summary: systemd-nspawn: No proper error handling when pointing
                    --bind to non-existent directory
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: mail at eliasprobst.eu
        QA Contact: systemd-bugs at lists.freedesktop.org

When pointing --bind to a non-existent directory, systemd-nspawn will fail with
"Failed to register machine: Interrupted system call" but doesn't show any
clear message why it failed.

systemd-nspawn should check the validity of a path in --bind before attempting
to launch the instance.
If the path is invalid, it should show an error message like:
"Path /foo/bar is invalid"


The same goes for --bind-ro

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150204/59e7ec7e/attachment.html>


More information about the systemd-bugs mailing list