Marked Xenial series as 'Fix Released' since the fix, commit
b9a985db98961ae1ba0be169f19df1c567e4ffe0 upstream (pid_ns: Sleep in
TASK_INTERRUPTIBLE in zap_pid_ns_processes), has been included as part
of update to 4.4.70 stable release (bug #1694621).

** Changed in: linux (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification

  Impact: In some cases some docker processes can be stuck in the D
  state after a container has terminated. They will remain in this state
  until reboot.

  Fix: Cherry pick upstream commit
  b9a985db98961ae1ba0be169f19df1c567e4ffe0, which has already been
  included as a stable commit in maintained upstream stable kernels.

  Test case: See below.

  Regression potential: Low, this is a simple change and as stated above
  the patch has already been shipped out in upstream stable kernels.


  (please refer to for

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
   total 0
   crw-rw---- 1 root audio 116,  1 May 29 16:54 seq
   crw-rw---- 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)

   PATH=(custom, no user)
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware                            1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)

  _MarkForUpload: True 02/16/2017
  dmi.bios.vendor: Xen
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: HVM domU
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to