Ok, I just tried with this version, and the issue I am seeing sadly does
persist. So, this does not resolve it. Please ignore the last comment.
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:
Status in systemd source package in Xenial:
Status in systemd source package in Zesty:
Status in systemd source package in Artful:
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
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: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp