Thanks for porting this to Xenial. Should the Xenial Ubuntu Base release be updated? The Ubuntu Base 16.04.3 does come with the problematic systemd, and on some systems, like the armhf, booting to a bare rootfs is impossible (always get the issue, which manifest itself as 'A start job is running for dev-ttys0.device' message and hang pretty much right after the 1:30 minute delay timeout.
Or, without releasing an Ubuntu Base update, the documentation (Wiki) probably should include a note on this (i.e. 'To document'). qemu could be used to update the systemd package, or possibly downloading and manually updating the newer systemd related files to the extracted rootfs. Regards, Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709649 Title: 229 backport for race between explicit mount and handling automount Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] In systemd prior to 234 a race exists between .mount and .automount units such that automount requests from kernel may not be serviced by systemd resulting in kernel holding the mountpoint and any processes that try to use said mount will hang. A race like this may lead to denial of service, until mount points are unmounted. [Testcase] Create a race between .mount and .automount units, such that automout request is serviced after .mount unit has been started. Observe a hang. More detailed steps are available at https://github.com/systemd/systemd/pull/5916 [Butfix] Cherrypick upstream commit https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318 [Regression Potential] The underlying logic of starting/stopping/triggering units is unchanged. However, there the logic as to when to send automout_send_ready() is relaxed, such that it is always sent whenever unit is already mounted. This is done to explicitly cope with late arrival of the incoming [aircraft] automount request. [Original Bug report / request] Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp