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


You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  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:
  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.

  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

  Cherrypick upstream commit

  [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]


  We have a blocking issue in systemd for the following release

  VERSION="16.04.3 LTS (Xenial Xerus)"
  PRETTY_NAME="Ubuntu 16.04.3 LTS"

  This release runs systemd229, we are affected by the following auto-
  mouting race condition


  Is back porting  the fix to the release 229 an option?


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to