This bug was fixed in the package systemd - 232-21ubuntu7

---------------
systemd (232-21ubuntu7) zesty; urgency=medium

  * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
  * networkd: add support for ActiveSlave and PrimarySlave netdev options.
    (LP: #1709135)
  * Cherrypick upstream fix for a race between .mount and .automount units,
    which currently may result in automounts hanging. (LP: #1709649)
  * systemd.postinst: Fix-up version number check in the previous sru.
    The version check in the postinst was too tight, thus the SRU fix failed
    validation. (LP: #1710410)

systemd (232-21ubuntu6) zesty; urgency=medium

  * link: Fix offload features initialization.
    This fixes a regression introduced in v232 which caused TCP
    segmentation offloads being disabled by default, resulting in
    significant performance issues under certain conditions. (Closes: #864073)
    (LP: #1703393)
  * loginctl: Fix loginctl ignoring user given session IDs at command-line
    (LP: #1682154)
  * Disable fallback DNS servers.
    This causes resolved to call-home to google, attempt to access network when
    none is available, and spams logs. (LP: #1449001)
  * initramfs-tools: trigger udevadm add actions with subsystems first.
    This updates the initramfs-tools init-top udev script to trigger udevadm
    actions with type specified. This mimicks the
    systemd-udev-trigger.service. Without type specified only devices are
    triggered, but triggering subsystems may also be required and should happen
    before triggering the devices. This is the case for example on s390x with 
zdev
    generated udev rules. (LP: #1713536)
  * Enable systemd-resolved by default. (LP: #1710410)
  * core: fix systemd failing to serialize tasks correctly on daemon-reload.
    (LP: #1702823)

 -- Dimitri John Ledkov <x...@ubuntu.com>  Wed, 04 Oct 2017 14:22:02
+0100

** Changed in: systemd (Ubuntu Zesty)
       Status: Fix Committed => Fix Released

-- 
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:
  Triaged
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     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to