[Kernel-packages] [Bug 1998602] acpidump.txt

[Serge Hallyn]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634729/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] WifiSyslog.txt

[Serge Hallyn]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634728/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] UdevDb.txt

[Serge Hallyn]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634727/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] RfKill.txt

[Serge Hallyn]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634726/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] PulseList.txt

[Serge Hallyn]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634725/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] ProcModules.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634724/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] ProcInterrupts.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634723/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] ProcCpuinfoMinimal.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634722/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] ProcCpuinfo.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634721/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] PaInfo.txt

[Serge Hallyn]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634720/+files/PaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Lsusb-v.txt

[Serge Hallyn]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634719/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Lsusb.txt

[Serge Hallyn]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634717/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Lsusb-t.txt

[Serge Hallyn]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634718/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Lspci-vt.txt

[Serge Hallyn]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634716/+files/Lspci-vt.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] IwConfig.txt

[Serge Hallyn]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634714/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Lspci.txt

[Serge Hallyn]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634715/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] CurrentDmesg.txt

[Serge Hallyn]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634712/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] HookError_ubuntu.txt

[Serge Hallyn]

apport information

** Attachment added: "HookError_ubuntu.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634713/+files/HookError_ubuntu.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] CRDA.txt

[Serge Hallyn]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1998602/+attachment/5634711/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  3929 F pulseaudio
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-25 (283 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XXS3JC01
  Package: linux (not installed)
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.52
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET76W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS3JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS3JC01
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] Re: overlay writing user.* xattrs on symlinks

[Serge Hallyn]

apport information

** Tags added: apport-collected jammy

** Description changed:

  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.
  
  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline
  build (6.1.0-060100rc5-generic), an unprivileged program can cause such
  xattrs to be created.  Once they're there, userspace (i.e. setfattr)
  cannot remove them since the kernel says they can't exist - but
  listxattr shows them.
  
  I've failed so far in setting up a simpler reproducer, so I'll begin by
  reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:
  
  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd
  
  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF
  
  and run 'stacker build'.  It will end with:
  
  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1
  
  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.
  
- I had thought I should be able to reproduce it by mounting (in an
- unprivileged user+mountns) an overlayfs where the underlay has, say,
- "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl
- disable dnsmasq is doing), but that did not work for me.
+ I had thought I should be able to reproduce it by mounting (in an 
unprivileged user+mountns) an overlayfs where the underlay has, say, 
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl disable 
dnsmasq is doing), but that did not work for me.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  serge  3929 F pulseaudio
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-02-25 (283 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ MachineType: LENOVO 20XXS3JC01
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=st-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-56-generic N/A
+  linux-backports-modules-5.15.0-56-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.7
+ Tags:  jammy
+ Uname: Linux 5.15.0-56-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-03-16 (264 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/08/2022
+ dmi.bios.release: 1.52
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N32ET76W (1.52 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20XXS3JC01
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.32
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET76W(1.52):bd04/08/2022:br1.52:efr1.32:svnLENOVO:pn20XXS3JC01:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS3JC01:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
+ dmi.product.family: ThinkPad X1 Carbon Gen 9
+ dmi.product.name: 20XXS3JC01
+ dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
+ dmi.product.version: ThinkPad X1 Carbon Gen 9
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1998602/+attachment/5634710/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 

[Kernel-packages] [Bug 1998602] Re: overlay writing user.* xattrs on symlinks

[Serge Hallyn]

> Fwiw, I think you need index=on enabled for origin xattrs to be set.

Did try that, no difference.  Anyway I probably just need to take a
closer look at what exact operations are done under /etc/rc*.d when
disabling a service... I'm sure I'm missing something obvious.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an
  unprivileged user+mountns) an overlayfs where the underlay has, say,
  "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl
  disable dnsmasq is doing), but that did not work for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998602] [NEW] overlay writing user.* xattrs on symlinks

[Serge Hallyn]

Public bug reported:

This was reported (and worked around) in https://github.com/project-
stacker/stacker/pull/333.

The kernel does not allow user.* xattrs on a symlink.  However, on
5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu mainline
build (6.1.0-060100rc5-generic), an unprivileged program can cause such
xattrs to be created.  Once they're there, userspace (i.e. setfattr)
cannot remove them since the kernel says they can't exist - but
listxattr shows them.

I've failed so far in setting up a simpler reproducer, so I'll begin by
reporting the full reproducer.  Download 'stacker' from
https://github.com/project-
stacker/stacker/releases/download/v0.22.1/stacker .  Create a
stacker.yaml config file:

cat > stacker.yaml << EOF
pxe-server-base:
from:
type: docker
url: docker://ubuntu:jammy
run: |
apt-get update
apt-get -y install dnsmasq systemd

sb-pxe-server:
from:
type: built
tag: pxe-server-base
run: |
  systemctl disable dnsmasq
EOF

and run 'stacker build'.  It will end with:

Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
error: exit status 1

You'll subsequently see that ./roots/sb-pxe-
server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
user.overlay.origin xattr (per llistxatr), though you can't read the
contents or delete it.

I had thought I should be able to reproduce it by mounting (in an
unprivileged user+mountns) an overlayfs where the underlay has, say,
"/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl
disable dnsmasq is doing), but that did not work for me.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998602

Title:
  overlay writing user.* xattrs on symlinks

Status in linux package in Ubuntu:
  New

Bug description:
  This was reported (and worked around) in https://github.com/project-
  stacker/stacker/pull/333.

  The kernel does not allow user.* xattrs on a symlink.  However, on
  5.15.0-53-generic and 5.19.0-21-generic, but not on the ubuntu
  mainline build (6.1.0-060100rc5-generic), an unprivileged program can
  cause such xattrs to be created.  Once they're there, userspace (i.e.
  setfattr) cannot remove them since the kernel says they can't exist -
  but listxattr shows them.

  I've failed so far in setting up a simpler reproducer, so I'll begin
  by reporting the full reproducer.  Download 'stacker' from
  https://github.com/project-
  stacker/stacker/releases/download/v0.22.1/stacker .  Create a
  stacker.yaml config file:

  cat > stacker.yaml << EOF
  pxe-server-base:
  from:
  type: docker
  url: docker://ubuntu:jammy
  run: |
  apt-get update
  apt-get -y install dnsmasq systemd

  sb-pxe-server:
  from:
  type: built
  tag: pxe-server-base
  run: |
systemctl disable dnsmasq
  EOF

  and run 'stacker build'.  It will end with:

  Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
  Removed /etc/systemd/system/multi-user.target.wants/dnsmasq.service.
  error: /home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq: 
failed to remove attr user.overlay.origin: xattr.LRemove 
/home/ubuntu/build2/roots/sb-pxe-server/overlay/etc/rc2.d/K01dnsmasq 
user.overlay.origin: operation not permitted
  error: exit status 1

  You'll subsequently see that ./roots/sb-pxe-
  server/overlay/etc/rc2.d/K01dnsmasq is a symbolic link with
  user.overlay.origin xattr (per llistxatr), though you can't read the
  contents or delete it.

  I had thought I should be able to reproduce it by mounting (in an
  unprivileged user+mountns) an overlayfs where the underlay has, say,
  "/etc/rc2.d/K" symlink, then rename K to S (as i assume the 'systemctl
  disable dnsmasq is doing), but that did not work for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998602/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Re: nbd ( + lvm thin pool?) fragile

[Serge Hallyn]

*** This bug is a duplicate of bug 1628336 ***
https://bugs.launchpad.net/bugs/1628336

** This bug has been marked a duplicate of bug 1628336
   mount-image-callback cannot mount partitioned disk image

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to
  track down with this test script, but it's possible, not certain, that
  those all boil down to having to manually dmremove the devices)

   reproduction script:

  #!/bin/bash -exu

  modprobe nbd
  rm -f nbd.img

  cleanup() {
  if [ $failed -eq 1 ]; then
  echo "XXX"
  lvscan
  echo "XX"
  vgchange -an nbd || true
  qemu-nbd -d /dev/nbd0
  dmsetup remove nbd-ThinDataLV || true
  dmsetup remove nbd-ThinDataLV_tmeta || true
  dmsetup remove nbd-ThinDataLV_tdata || true
  fi
  }

  truncate -s 30G nbd.img

  sfdisk nbd.img << EOF
  , 2G;
  ,,8e;
  EOF

  vg=nbd
  thinsize=20G

  sync

  echo "Connecting empty file"

  qemu-nbd -f raw -c /dev/nbd0 nbd.img

  failed=1
  trap cleanup EXIT

  echo "Creating partition 1"
  mkfs.ext4 /dev/nbd0p1
  mount /dev/nbd0p1 /mnt
  touch /mnt/helloworld
  umount /mnt

  echo "Creating LVM partitions"
  pvscan --cache
  pvcreate -ff /dev/nbd0p2
  vgcreate nbd /dev/nbd0p2

  lvcreate -n ThinDataLV -L "${thinsize}" "${vg}"
  lvcreate -n MetaDataLV -L 1G "${vg}"
  lvconvert -y --type thin-pool --poolmetadata "${vg}/MetaDataLV" 
"${vg}/ThinDataLV"

  sleep 5
  sync
  sleep 5

  echo "Disconnecting first"
  cleanup

  # now verify

  echo "Reconnecting to verify"
  qemu-nbd -f raw -c /dev/nbd0 nbd.img

  echo "Mounting,"
  mount /dev/nbd0p1 /mnt
  echo "Checking whether helloworld file is there"
  test -f /mnt/helloworld
  echo "unmounting,"
  umount /mnt
  echo "disconnecting,"

  cleanup

  echo "Done"
  failed=0

  echo PASS


  ---
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.

   ens33 no wireless extensions.

   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Re: nbd ( + lvm thin pool?) fragile

[Serge Hallyn]

Well, actually on virtualbox it's touch-and-go.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to
  track down with this test script, but it's possible, not certain, that
  those all boil down to having to manually dmremove the devices)

   reproduction script:

  #!/bin/bash -exu

  modprobe nbd
  rm -f nbd.img

  cleanup() {
  if [ $failed -eq 1 ]; then
  echo "XXX"
  lvscan
  echo "XX"
  vgchange -an nbd || true
  qemu-nbd -d /dev/nbd0
  dmsetup remove nbd-ThinDataLV || true
  dmsetup remove nbd-ThinDataLV_tmeta || true
  dmsetup remove nbd-ThinDataLV_tdata || true
  fi
  }

  truncate -s 30G nbd.img

  sfdisk nbd.img << EOF
  , 2G;
  ,,8e;
  EOF

  vg=nbd
  thinsize=20G

  sync

  echo "Connecting empty file"

  qemu-nbd -f raw -c /dev/nbd0 nbd.img

  failed=1
  trap cleanup EXIT

  echo "Creating partition 1"
  mkfs.ext4 /dev/nbd0p1
  mount /dev/nbd0p1 /mnt
  touch /mnt/helloworld
  umount /mnt

  echo "Creating LVM partitions"
  pvscan --cache
  pvcreate -ff /dev/nbd0p2
  vgcreate nbd /dev/nbd0p2

  lvcreate -n ThinDataLV -L "${thinsize}" "${vg}"
  lvcreate -n MetaDataLV -L 1G "${vg}"
  lvconvert -y --type thin-pool --poolmetadata "${vg}/MetaDataLV" 
"${vg}/ThinDataLV"

  sleep 5
  sync
  sleep 5

  echo "Disconnecting first"
  cleanup

  # now verify

  echo "Reconnecting to verify"
  qemu-nbd -f raw -c /dev/nbd0 nbd.img

  echo "Mounting,"
  mount /dev/nbd0p1 /mnt
  echo "Checking whether helloworld file is there"
  test -f /mnt/helloworld
  echo "unmounting,"
  umount /mnt
  echo "disconnecting,"

  cleanup

  echo "Done"
  failed=0

  echo PASS


  ---
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.

   ens33 no wireless extensions.

   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Re: nbd ( + lvm thin pool?) fragile

[Serge Hallyn]

http://pastebin.com/raw/YPGG6usG   is the reproduction script.

In virtualbox it actually passes.  Maybe this really is a problem with
the disk driver for vmware?

** Description changed:

  I've been trying this on several platforms -
  
  16.04 physical host
  16.04 VMware
  17.04 vmware
  
  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.
  
  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).
  
  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The file
  /dev/nbd0p1 does not exist and no size was specified."
  
- (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
- --- 
+ (I've had other - corruption - issues which are what I was trying to
+ track down with this test script, but it's possible, not certain, that
+ those all boil down to having to manually dmremove the devices)
+ 
+  reproduction script:
+ 
+ #!/bin/bash -exu
+ 
+ modprobe nbd
+ rm -f nbd.img
+ 
+ cleanup() {
+ if [ $failed -eq 1 ]; then
+ echo "XXX"
+ lvscan
+ echo "XX"
+ vgchange -an nbd || true
+ qemu-nbd -d /dev/nbd0
+ dmsetup remove nbd-ThinDataLV || true
+ dmsetup remove nbd-ThinDataLV_tmeta || true
+ dmsetup remove nbd-ThinDataLV_tdata || true
+ fi
+ }
+ 
+ truncate -s 30G nbd.img
+ 
+ sfdisk nbd.img << EOF
+ , 2G;
+ ,,8e;
+ EOF
+ 
+ vg=nbd
+ thinsize=20G
+ 
+ sync
+ 
+ echo "Connecting empty file"
+ 
+ qemu-nbd -f raw -c /dev/nbd0 nbd.img
+ 
+ failed=1
+ trap cleanup EXIT
+ 
+ echo "Creating partition 1"
+ mkfs.ext4 /dev/nbd0p1
+ mount /dev/nbd0p1 /mnt
+ touch /mnt/helloworld
+ umount /mnt
+ 
+ echo "Creating LVM partitions"
+ pvscan --cache
+ pvcreate -ff /dev/nbd0p2
+ vgcreate nbd /dev/nbd0p2
+ 
+ lvcreate -n ThinDataLV -L "${thinsize}" "${vg}"
+ lvcreate -n MetaDataLV -L 1G "${vg}"
+ lvconvert -y --type thin-pool --poolmetadata "${vg}/MetaDataLV" 
"${vg}/ThinDataLV"
+ 
+ sleep 5
+ sync
+ sleep 5
+ 
+ echo "Disconnecting first"
+ cleanup
+ 
+ # now verify
+ 
+ echo "Reconnecting to verify"
+ qemu-nbd -f raw -c /dev/nbd0 nbd.img
+ 
+ echo "Mounting,"
+ mount /dev/nbd0p1 /mnt
+ echo "Checking whether helloworld file is there"
+ test -f /mnt/helloworld
+ echo "unmounting,"
+ umount /mnt
+ echo "disconnecting,"
+ 
+ cleanup
+ 
+ echo "Done"
+ failed=0
+ 
+ echo PASS
+ 
+ 
+ ---
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  serge  1399 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
-  lxcbr0no wireless extensions.
-  
-  ens33 no wireless extensions.
-  
-  lono wireless extensions.
+  lxcbr0no wireless extensions.
+ 
+  ens33 no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-37-generic N/A
-  linux-backports-modules-4.10.0-37-generic  N/A
-  linux-firmware 1.164.1
+  linux-restricted-modules-4.10.0-37-generic N/A
+  linux-backports-modules-4.10.0-37-generic  N/A
+  linux-firmware 1.164.1
  RfKill:
-  1: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  1: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: 

[Kernel-packages] [Bug 1728109] ProcModules.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998191/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] WifiSyslog.txt

[Serge Hallyn]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998194/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] UdevDb.txt

[Serge Hallyn]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1728109/+attachment/4998193/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] PulseList.txt

[Serge Hallyn]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998192/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Lsusb.txt

[Serge Hallyn]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1728109/+attachment/4998186/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] ProcCpuinfoMinimal.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998188/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] ProcInterrupts.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998190/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] ProcCpuinfo.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998187/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] ProcEnviron.txt

[Serge Hallyn]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998189/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Lspci.txt

[Serge Hallyn]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1728109/+attachment/4998185/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] JournalErrors.txt

[Serge Hallyn]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998184/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] CurrentDmesg.txt

[Serge Hallyn]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998183/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] CRDA.txt

[Serge Hallyn]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1728109/+attachment/4998182/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1728109] Re: nbd ( + lvm thin pool?) fragile

[Serge Hallyn]

apport information

** Tags added: apport-collected zesty

** Description changed:

  I've been trying this on several platforms -
  
  16.04 physical host
  16.04 VMware
  17.04 vmware
  
  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.
  
  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).
  
  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The file
  /dev/nbd0p1 does not exist and no size was specified."
  
- (I've had other - corruption - issues which are what I was trying to
- track down with this test script, but it's possible, not certain, that
- those all boil down to having to manually dmremove the devices)
+ (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  serge  1399 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-09-15 (41 days ago)
+ InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ IwConfig:
+  lxcbr0no wireless extensions.
+  
+  ens33 no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
+ ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-37-generic N/A
+  linux-backports-modules-4.10.0-37-generic  N/A
+  linux-firmware 1.164.1
+ RfKill:
+  1: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  zesty
+ Uname: Linux 4.10.0-37-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/19/2017
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: No Enclosure
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
+ dmi.product.name: VMware Virtual Platform
+ dmi.product.version: None
+ dmi.sys.vendor: VMware, Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1728109/+attachment/4998181/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to track 
down with this test script, but it's possible, not certain, that those all boil 
down to having to manually dmremove the devices)
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serge  1399 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-15 (41 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lxcbr0no wireless extensions.
   
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=c33e6872-2e16-4b10-8d42-9dfacd6a132b ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1728109] [NEW] nbd ( + lvm thin pool?) fragile

[Serge Hallyn]

Public bug reported:

I've been trying this on several platforms -

16.04 physical host
16.04 VMware
17.04 vmware

The script pasted below creates a virtual disk, writes a partition
table, creates an fs and some thin pools, then verifies that writes
happened as expected.

On 16.04 physical host it seems to be working (though I do need to
manually dmremove the devices as seen in cleanup(), else a second run
fails).

On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The file
/dev/nbd0p1 does not exist and no size was specified."

(I've had other - corruption - issues which are what I was trying to
track down with this test script, but it's possible, not certain, that
those all boil down to having to manually dmremove the devices)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728109

Title:
  nbd ( + lvm thin pool?) fragile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying this on several platforms -

  16.04 physical host
  16.04 VMware
  17.04 vmware

  The script pasted below creates a virtual disk, writes a partition
  table, creates an fs and some thin pools, then verifies that writes
  happened as expected.

  On 16.04 physical host it seems to be working (though I do need to
  manually dmremove the devices as seen in cleanup(), else a second run
  fails).

  On the VMware hosted vms, the mkfs.ext4 fails to find nbd0p1:  "The
  file /dev/nbd0p1 does not exist and no size was specified."

  (I've had other - corruption - issues which are what I was trying to
  track down with this test script, but it's possible, not certain, that
  those all boil down to having to manually dmremove the devices)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728109/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

[Serge Hallyn]

I've seen reports that this is fixed in 4.10?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/882147

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

[Serge Hallyn]

Nope, tail -f is still broken at least in 4.12.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/882147

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1641168] Re: packaging error in yakkety kernel source causing failure to build

[Serge Hallyn]

Just re-tested.  The z kernel builds fine.  the yakkety-proposed kernel
still fails to build:

cc1: fatal error: 
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
 No such file or directory
compilation terminated.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1641168

Title:
  packaging error in yakkety kernel source causing failure to build

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to build the kernel source from yakkety-updates locally, I
  get failure like:

  cc1: fatal error:
  
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1641168] Re: packaging error in yakkety kernel source causing failure to build

[Serge Hallyn]

** Tags added: bot-stop-nagging

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1641168

Title:
  packaging error in yakkety kernel source causing failure to build

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I try to build the kernel source from yakkety-updates locally, I
  get failure like:

  cc1: fatal error:
  
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1641168] [NEW] packaging error in yakkety kernel source causing failure to build

[Serge Hallyn]

Public bug reported:

When I try to build the kernel source from yakkety-updates locally, I
get failure like:

cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1641168

Title:
  packaging error in yakkety kernel source causing failure to build

Status in linux package in Ubuntu:
  New

Bug description:
  When I try to build the kernel source from yakkety-updates locally, I
  get failure like:

  cc1: fatal error:
  
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1448269] Re: qemu guest hangs on nested kvm startup with host kernel oops

[Serge Hallyn]

Please open a new bug - thanks.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1448269

Title:
  qemu guest hangs on nested kvm startup with host kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Users of nested KVM may experience the L1 VM hanging when booting an L2 VM. 
Overall this seems to be due to issues with external interrupts not reaching L1 
when L2 gets booted.

  [Test Case]
  Run a nested KVM instance:
  https://gist.github.com/arges/9d21c6da03a8c10d3980

  [Fix]
  commit 4fa7734c62cdd8c07edd54fa5a5e91482273071a
  commit f3380ca5d7edb5e31932998ab2e29dfdce39c5ed

  --

  I'm creating a vivid qemu guest on a trusty host with
  3.13.0-48-generic kernel.  When I start a guest inside that guest, I
  get the oops below on the host while the first guest hangs and must be
  (virsh) destroyed.

  Apr 24 20:40:08 sergeh2 kernel: [1575627.844208] [ cut here 
]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844227] WARNING: CPU: 2 PID: 17176 
at /build/buildd/linux-3.13.0/arch/x86/kvm/vmx.c:8414 
nested_vmx_vmexit+0x11c/0x150 [kvm_intel]()
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844229] Modules linked in: vhost_net 
vhost macvtap macvlan xts gf128mul xt_conntrack ipt_REJECT ip6table_filter 
ip6_tables ebtable_nat ebtables veth xt_nat xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE
  iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt gpio_ich 
coretemp kvm_intel kvm i7core_edac edac_core lpc_ich shpchp mac_hid serio_raw 
lp parp
  ort btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq raid0 multipath linear dm_snapshot raid1 
nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper drm ahci r8169 libahci 
mii wmi
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844281] CPU: 2 PID: 17176 Comm: 
qemu-system-x86 Not tainted 3.13.0-48-generic #80-Ubuntu
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844283] Hardware name: MSI 
MS-7522/MSI X58 Pro (MS-7522)  , BIOS V8.14B8 11/09/2012
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844286]  0009 
880907561c98 81721506 
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844290]  880907561cd0 
810677dd 880bfa808000 0014
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844293]  8806da7a7000 
880bfca9c800  880907561ce0
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844297] Call Trace:
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844305]  [] 
dump_stack+0x45/0x56
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844310]  [] 
warn_slowpath_common+0x7d/0xa0
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844314]  [] 
warn_slowpath_null+0x1a/0x20
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844321]  [] 
nested_vmx_vmexit+0x11c/0x150 [kvm_intel]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844327]  [] 
vmx_queue_exception+0xfd/0x140 [kvm_intel]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844347]  [] 
vcpu_enter_guest+0x9f0/0xce0 [kvm]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844364]  [] 
kvm_arch_vcpu_ioctl_run+0x1e8/0x460 [kvm]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844376]  [] 
kvm_vcpu_ioctl+0x2a2/0x5e0 [kvm]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844381]  [] ? 
__wake_up_common+0x58/0x90
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844387]  [] ? 
fsnotify+0x241/0x320
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844391]  [] 
do_vfs_ioctl+0x2e0/0x4c0
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844406]  [] ? 
kvm_on_user_return+0x74/0x80 [kvm]
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844409]  [] 
SyS_ioctl+0x81/0xa0
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844414]  [] 
system_call_fastpath+0x1a/0x1f
  Apr 24 20:40:08 sergeh2 kernel: [1575627.844416] ---[ end trace 
351396e62b6ef224 ]---
  Apr 24 20:48:29 sergeh2 dnsmasq-dhcp[1409]: DHCPREQUEST(lxcbr0) 10.0.3.104 
00:16:3e:72:73:32

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 14:22 seq
   crw-rw 1 root audio 116, 33 Apr 10 14:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri 

[Kernel-packages] [Bug 1603902] Re: qemu-img convert hangs on Ubuntu Server 16.04 with 100% cpu

[Serge Hallyn]

Thanks for the info.

If updating kernels fixes it, then it's possible, but unlikely, that it
can be fixed in userspace.  Marking this as affecting the kernel.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1603902

Title:
  qemu-img convert hangs on Ubuntu Server 16.04 with 100% cpu

Status in linux package in Ubuntu:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  New

Bug description:

  When i try to convert raw image to qcow2 format with command:

  qemu-img convert -O qcow2 base-image.img base-image.qcow2

  i have several problems:

  1.qemu-img process never stops by itself and i can not kill it with kill 
-9
  2.qemu-img process utilizes 100% of one cpu core

  Additional information:

  1.I use supermicro server with 28 cpu cores and host Ubuntu Server 16.04
  2.Filesystem is ext4
  3.Original VM raw image (with installed guest Ubuntu Server 16.04) works 
without any problem. When i am trying to convert formats this VM is powered off.

  4.uname -r
  4.4.0-28-generic

  
  dpkg -s qemu-kvm | grep Version
  Version: 1:2.5+dfsg-5ubuntu10.2

  
  dpkg -s qemu-utils | grep Version
  Version: 1:2.5+dfsg-5ubuntu10.2

  
  strace qemu-img convert -O qcow2 base-image.img base-image.qcow2 
  ...
  lseek(10, 1361051648, SEEK_DATA)= 1386217472
  lseek(10, 1386217472, SEEK_DATA)= 1386217472
  lseek(10, 1386217472, SEEK_HOLE)= 1403359232
  lseek(10, 1403359232, SEEK_DATA)= 1403387904
  lseek(10, 1403387904, SEEK_DATA)= 1403387904
  lseek(10, 1403387904, SEEK_HOLE)= 1419091968
  lseek(10, 1419091968, SEEK_DATA

  What can cause such strange behavior, and how can i convert raw image
  to qcow2 format?

  UPDATED: I have installed 4.6.0 linux kernel, and everything works
  fine right now. But the question still exists: is there any other way
  to fix this bug for qemu-img and Ubuntu 16.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1602443] Re: Bad page state in qemu-system-x86 process

[Serge Hallyn]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1602443

Title:
  Bad page state in qemu-system-x86 process

Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  BUG: Bad page state in process qemu-system-x86

  [ 2284.443389] Call Trace:
  [ 2284.443398]  [] dump_stack+0x63/0x90
  [ 2284.443404]  [] bad_page.part.68+0xae/0x100
  [ 2284.443408]  [] free_pages_prepare+0x2e6/0x310
  [ 2284.443413]  [] ? uncharge_list+0xc1/0xd0
  [ 2284.443417]  [] free_hot_cold_page+0x35/0x1c0
  [ 2284.443422]  [] put_page+0x40/0x50
  [ 2284.443428]  [] dio_bio_complete+0x77/0xc0
  [ 2284.443432]  [] do_blockdev_direct_IO+0x23bf/0x3410
  [ 2284.443435]  [] ? mempool_free_slab+0x17/0x20
  [ 2284.443440]  [] ? I_BDEV+0x20/0x20
  [ 2284.443443]  [] __blockdev_direct_IO+0x43/0x50
  [ 2284.443447]  [] blkdev_direct_IO+0x58/0x80
  [ 2284.443461]  [] generic_file_read_iter+0x47b/0x5c0
  [ 2284.443465]  [] ? hrtimer_cancel+0x19/0x20
  [ 2284.443472]  [] ? futex_wait+0x206/0x280
  [ 2284.443476]  [] blkdev_read_iter+0x35/0x40
  [ 2284.443482]  [] do_iter_readv_writev+0x6c/0xa0
  [ 2284.443486]  [] do_readv_writev+0x18f/0x230
  [ 2284.443492]  [] ? wake_up_q+0x70/0x70
  [ 2284.443496]  [] vfs_readv+0x36/0x50
  [ 2284.443501]  [] SyS_preadv+0xc5/0xe0

  
  There are VMs running on qemu/kvm with root fs mounted from AoE storage 
volumes.
   
  Contact Information = John Keenleyside keen...@ca.ibm.com; David Wright 
ddwri...@us.ibm.com 
   
  ---uname output---
  Linux h0102-u07 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = Supermicro SYS-1028U-TNRTP+ 

  The reporter was requested to provide recreation steps and sosreport
  and also report the problem in parallel with Supermicro.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602443/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1584163] Re: cgroup namespace update

[Serge Hallyn]

How do you figure verification needed?  See comment #3.

** Tags removed: verification-needed-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584163

Title:
  cgroup namespace update

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

Bug description:
   During xenial cycle we applied a patch (and a followon fix for criu)
  to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
  Since then, the approach to fix it upstream has changed.  Please revert
  the two nsroot patches currently in xenial and yakkety, and replace them
  with the new patches.

  Impact:
  One or the other of these patchsets suffices for docker in lxd to work.
  The patchset being reverted required a docker patch, the new one does
  not.  Docker cannot work inside lxd with neither patchset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584163/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Serge Hallyn]

I recommend opening new bugs against libvirt and docker.  Libvirt moves
VMS into a cpuset by default.  I assume docker does the same.  (My
xenial laptop runs upstart, so this is not systemd's doing)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1392176

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Serge Hallyn]

"LXC cases, like docker and KVM" - did you mean non-lxc cases?

xenial by default should now be using libpam-cgfs, should not be using
cgmanager, and should not be creating cpusets.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1392176

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1584163] Re: cgroup namespace update

[Serge Hallyn]

With xenial kernel:

132 125 0:57 /lxc/x1 /sys/fs/cgroup/blkio
rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,blkio,nsroot=/lxc/x1

with xenial-proposed kernel:

134 125 0:59 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime -
cgroup cgroup rw,blkio


** Tags removed: verification-needed-xenial
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584163

Title:
  cgroup namespace update

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed

Bug description:
   During xenial cycle we applied a patch (and a followon fix for criu)
  to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
  Since then, the approach to fix it upstream has changed.  Please revert
  the two nsroot patches currently in xenial and yakkety, and replace them
  with the new patches.

  Impact:
  One or the other of these patchsets suffices for docker in lxd to work.
  The patchset being reverted required a docker patch, the new one does
  not.  Docker cannot work inside lxd with neither patchset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584163/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1584163] [NEW] cgroup namespace update

[Serge Hallyn]

Public bug reported:

 During xenial cycle we applied a patch (and a followon fix for criu)
to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
Since then, the approach to fix it upstream has changed.  Please revert
the two nsroot patches currently in xenial and yakkety, and replace them
with the new patches.

Impact:
One or the other of these patchsets suffices for docker in lxd to work.
The patchset being reverted required a docker patch, the new one does
not.  Docker cannot work inside lxd with neither patchset.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584163

Title:
  cgroup namespace update

Status in linux package in Ubuntu:
  New

Bug description:
   During xenial cycle we applied a patch (and a followon fix for criu)
  to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
  Since then, the approach to fix it upstream has changed.  Please revert
  the two nsroot patches currently in xenial and yakkety, and replace them
  with the new patches.

  Impact:
  One or the other of these patchsets suffices for docker in lxd to work.
  The patchset being reverted required a docker patch, the new one does
  not.  Docker cannot work inside lxd with neither patchset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584163/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq

[Serge Hallyn]

** Changed in: lxc (Ubuntu Xenial)
   Status: Confirmed => Invalid

** No longer affects: lxc (Ubuntu Vivid)

** No longer affects: lxc (Ubuntu Wily)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1446906

Title:
  lxc container with postfix, permission denied on mailq

Status in linux package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxc source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * Users may encounter situations where they use applications, confined by
 AppArmor, that hit EACESS failures when attempting to operate on AF_UNIX
 stream sockets.

   * These failures typically occur when the confined applications attempts to
 read from an AF_UNIX stream socket when the other end of the socket has
 already been closed.

   * AppArmor is mistakenly denying the socket operations due to the socket
 shutdown operation making the sun_path no longer being available for
 AppArmor mediation after the socket is shutdown.

  [Test Case]

   The expected test case is:

   $ sudo apt-get install postfix # installing in 'local only' config is fine
   $ cat > bug-profile << EOF
   profile bug-profile flags=(attach_disconnected) {
 network,
 file,
   }
   EOF
   $ sudo apparmor_parser -r bug.profile 
   $ aa-exec -p bug-profile -- mailq
   Mail queue is empty

   A failed test case will see the mailq command exit with an error:

   $ aa-exec -p bug-profile -- mailq
   postqueue: warning: close: Permission denied

   and these denials will be found in the syslog:

   Jan 25 16:56:29 sec-vivid-amd64 kernel: [  241.096168] audit: type=1400 
audit(1453762589.727:29): apparmor="DENIED" operation="file_perm" 
profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
   Jan 25 16:56:29 sec-vivid-amd64 kernel: [  241.096175] audit: type=1400 
audit(1453762589.727:30): apparmor="DENIED" operation="file_perm" 
profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  [Regression Potential]

   * The changes are local to the path-based AF_UNIX stream socket mediation 
code
 so that limits the regression potential to some degree.

   * John Johansen authored the patch and I reviewed it. It is small and there's
 no obvious areas of concern to me regarding potential regressions.

  [Other Info]

   * None at this time

  [Original bug report]

  Hello,

  on three Vivid host, all of them up-to-date, I have the problem
  described here:

  https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223

  That bug report shows the problem was fixed, but it is not (at least
  on current Vivid)

  ii  linux-image-generic 3.19.0.15.14   amd64  Generic Linux kernel 
image
  ii  lxc 1.1.2-0ubuntu3 amd64  Linux Containers 
userspace tools
  ii  apparmor2.9.1-0ubuntu9 amd64  User-space parser 
utility for AppArmor

  Reproducible with:

  $ sudo lxc-create -n test -t ubuntu
  $ sudo lxc-start -n test

  (inside container)

  $ sudo apt-get install postfix
  $ mailq
  postqueue: warning: close: Permission denied

  dmesg shows:
  [82140.386109] audit: type=1400 audit(1429661150.086:17067): 
apparmor="DENIED" operation="file_perm" profile="lxc-container-default" 
name="public/showq" pid=27742 comm="postqueue" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoolook1913 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6
  InstallationDate: Installed on 2015-02-27 (53 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20150
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago)
  UserGroups: adm docker libvirtd lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN95WW(V9.00)
  dmi.board.asset.tag: No Asset Tag
  

[Kernel-packages] [Bug 1567167] Re: Ubuntu 15.10: tsc_offset is error for hot-plugged vcpu.

[Serge Hallyn]

Thanks for reporting this bug.  The 'kvm' package shouldn't really
exist.  The bug you're referring to is in the kernel kvm code, so I'm
marking it as affecting the kernel.  (If it were in the userspace qemu
package, then the 'qemu' package would be the right bug target).

** Package changed: kvm (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567167

Title:
  Ubuntu 15.10: tsc_offset is error for hot-plugged vcpu.

Status in linux package in Ubuntu:
  New

Bug description:
  1. when hot plug vcpu, KVM will call kvm_write_tsc set the new vcpu's
  tsc_offset to host tsc.  The new vcpu's tsc_offsets is greatly
  different from preallocated vcpu's tsc_offset.

  2. For redhat 6.x, the vm will show warning and turn off TSC clock.
  kernel: CPU 1 got hotplugged
  kernel: kvm-clock: cpu 1, msr 0:282367c1, secondary cpu clock
  kernel: TSC synchronization [CPU#0 -> CPU#1]:
  kernel: Measured 150076598781 cycles TSC warp between CPUs, turning off TSC 
clock.
  kernel: Marking TSC unstable due to check_tsc_sync_source failed

  3. I think should set the new vcpu's tsc_offset to
  kvm->arch.cur_tsc_offset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567167/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1567159] Re: Ubuntu 15.10: After hot plug vcpu, kvm_arch->use_master_clock will never be true.

[Serge Hallyn]

Thanks for reporting this bug. The 'kvm' package shouldn't really exist.
The bug you're referring to is in the kernel kvm code, so I'm marking it
as affecting the kernel. (If it were in the userspace qemu package, then
the 'qemu' package would be the right bug target).

** Package changed: kvm (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567159

Title:
  Ubuntu 15.10: After hot plug vcpu, kvm_arch->use_master_clock will
  never be true.

Status in linux package in Ubuntu:
  New

Bug description:
  1. In function kvm_write_tsc, when tsc first matched, do
  kvm->arch.nr_vcpus_matched_tsc++;

  2. In function pvclock_update_vm_gtod_copy, if vcpus_matched (also
  with other conditions meet), ka->use_master_clock will be true;

  3. After hot plug vcpu, kvm_arch_vcpu_postcreate and Qemu will call
  kvm_write_tsc for the new vcpu. Because the tsc will not match, so do
  kvm->arch.nr_vcpus_matched_tsc = 0;

  4. For other already existed vcpu will not call kvm_write_tsc, so will
  not do kvm->arch.nr_vcpus_matched_tsc++;

  5. So vcpus_matched in function pvclock_update_vm_gtod_copy will be
  false forever, this cause ka->use_master_clock will never be true;

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567159/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

@leftyfb - what exactly is IBM asking to verify?  Whether kvm works
under powervm?  Did smoser's info help?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

Ok so if I'm following this right there are two issues:

1. the bug reporter is using a powervm partition.  KVM cannot be used
there.  This is not a KVM bug.

2. the xenial cloud images have an outdated 4.2 kernel which doesn't
boot in kvm on powernv.  A workaround is to use the isos which do boot.
This is a cloud-images bug.

AFAICS there is no qemu bug here, so marking invalid for that package.

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade 

Re: [Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

If you can reproduce this with the ppc64 xenial iso or a rootfs
installed from that, using 4.4 kernel, please let us know.  Otherwise,
I think the fix will be for cloud images to be updated with a 4.4 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

4.4.0-16 also works.

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

Actually the clou dimages have a 4.2 kernel.   When I use a xenial beta2
iso which has 4.4.0-15-generic #31, it boots fine.  I can install, and I
can boot the installed image (with same kernel) just fine.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

Result of doing  qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=my-seed.img,if=virtio


** Attachment added: "crash.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563887/+attachment/4622485/+files/crash.png

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

[Serge Hallyn]

Hm - I can boot a wily cloud image, just not a xenial one.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563887

Title:
  qemu-system-ppc64 freezes on starting image on ppc64le

Status in QEMU:
  New
Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
  image as part of the certification process. This on an IBM ppc64le in
  PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
  is no error output.

  ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net 
nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine 
pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  WARNING: Image format was not specified for 'seed.iso' and probing guessed 
raw.
   Automatically detecting the format is dangerous for raw images, 
write operations on block 0 will be restricted.
   Specify the 'raw' format explicitly to remove the restrictions.

  SLOF **
  QEMU Starting
   Build Date = Jan 29 2016 18:58:37
   FW Version = buildd@ release 20151103
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/vty@7100
  Populating /vdevice/nvram@7101
  Populating /vdevice/l-lan@7102
  Populating /vdevice/v-scsi@7103
     SCSI: Looking for devices
    8200 CD-ROM   : "QEMU QEMU CD-ROM  2.5+"
  Populating /pci@8002000
   00 1800 (D) : 1af4 1001virtio [ block ]
   00 1000 (D) : 1af4 1001virtio [ block ]
   00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
   00  (D) : 1234 qemu vga
  No NVRAM common partition, re-initializing...
  Installing QEMU fb

  Scanning USB
    OHCI: initializing
  USB Keyboard
  USB mouse
  No console specified using screen & keyboard

    Welcome to Open Firmware

    Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
    This program and the accompanying materials are made available
    under the terms of the BSD License available at
    http://www.opensource.org/licenses/bsd-license.php

  Trying to load:  from: /pci@8002000/scsi@3 ...
  E3404: Not a bootable device!
  Trying to load:  from: /pci@8002000/scsi@2 ...   Successfully loaded
  Linux ppc64le
  #31-Ubuntu SMP F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic ppc64le
  ApportVersion: 2.20-0ubuntu3
  Architecture: ppc64el
  Date: Wed Mar 30 14:10:01 2016
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1172 2  0.0 [kvm-irqfd-clean]
   qemu-nbdSsl  0 0 13467 1  0.0 qemu-nbd -c /dev/nbd0 
xenial-server-cloudimg-ppc64el-disk1.img
   qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 
-display none -nographic -net nic -net 
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic 
root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
  ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
   2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
   3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
   4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
   5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc 
version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu 
Mar 24 22:31:14 UTC 2016
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  bootlist:
   /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
   
/pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
   
/pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512

[Kernel-packages] [Bug 1558897] Re: guest vm hangs

[Serge Hallyn]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558897

Title:
  guest vm hangs

Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  Mar 18 09:52:55 OUVS1 kernel: [67330.365272] WARNING: CPU: 1 PID: 5186 at 
/build/linux-WzbyTg/linux-4.4.0/arch/x86/kvm/vmx.c:8130 
vmx_handle_exit+0x9ed/0xc30 [kvm_intel]()
  Mar 18 09:52:55 OUVS1 kernel: [67330.365284] vmx: unexpected exit reason 0x3
  Mar 18 09:52:55 OUVS1 kernel: [67330.365310] Modules linked in: vhost_net 
vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack i
  pt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss xt_tcpudp 
iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_
  generic intel_rapl intel_powerclamp coretemp punit_atom_debug 
crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd snd_intel_sst_acpi snd_hda_intel snd_intel_sst_core 
snd_soc_rt5670 snd_soc_rl6
  231 snd_hda_codec snd_soc_sst_mfld_platform snd_soc_core mei_txe snd_hda_core 
mei lpc_ich snd_hwdep shpchp snd_compress ac97_bus nxp_nci_i2c 
snd_pcm_dmaengine nxp_nci snd_pcm nci nfc snd_timer 8250_fintek dw_dmac dwc3 
dw_dmac_core rfkill
  _gpio udc_core snd ulpi soundcore pwm_lpss_platform i2c_designware_platform 
i2c_designware_core 8250_dw pwm_lpss spi_pxa2xx_platform soc_button_array 
mac_hid kvm_intel kvm irqbypass autofs4 i915 i2c_algo_bit drm_kms_helper 
syscopyarea sy
  sfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci fjes video i2c_hid 
hid sdhci_acpi sdhci pinctrl_cherryview
  Mar 18 09:52:55 OUVS1 kernel: [67330.365476] CPU: 1 PID: 5186 Comm: 
qemu-system-x86 Not tainted 4.4.0-13-generic #29-Ubuntu
  Mar 18 09:52:55 OUVS1 kernel: [67330.365499] Hardware name: To be filled by 
O.E.M. To be filled by O.E.M./Aptio CRB, BIOS 5.11 08/22/2015
  Mar 18 09:52:55 OUVS1 kernel: [67330.365525]  0286 
6642abe7 88007610bc10 813e2483
  Mar 18 09:52:55 OUVS1 kernel: [67330.365549]  88007610bc58 
c0356528 88007610bc48 8107fe12
  Mar 18 09:52:55 OUVS1 kernel: [67330.365575]  0003 
880076958000  88007695b1a0
  Mar 18 09:52:55 OUVS1 kernel: [67330.365600] Call Trace:
  Mar 18 09:52:55 OUVS1 kernel: [67330.365635]  [] 
dump_stack+0x63/0x90
  Mar 18 09:52:55 OUVS1 kernel: [67330.365657]  [] 
warn_slowpath_common+0x82/0xc0
  Mar 18 09:52:55 OUVS1 kernel: [67330.365680]  [] 
warn_slowpath_fmt+0x5c/0x80
  Mar 18 09:52:55 OUVS1 kernel: [67330.365734]  [] ? 
kvm_sched_in+0x39/0x40 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365745]  [] 
vmx_handle_exit+0x9ed/0xc30 [kvm_intel]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365785]  [] ? 
kvm_write_guest_cached+0x68/0xc0 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365817]  [] ? 
kvm_lapic_sync_from_vapic+0xac/0x180 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365846]  [] 
vcpu_enter_guest+0x79d/0x1060 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365877]  [] ? 
kvm_apic_has_interrupt+0x45/0xc0 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365907]  [] 
kvm_arch_vcpu_ioctl_run+0xdf/0x400 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365935]  [] 
kvm_vcpu_ioctl+0x33d/0x620 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.365943]  [] ? 
do_futex+0x107/0x500
  Mar 18 09:52:55 OUVS1 kernel: [67330.365967]  [] ? 
wake_up_q+0x70/0x70
  Mar 18 09:52:55 OUVS1 kernel: [67330.365993]  [] 
do_vfs_ioctl+0x29f/0x490
  Mar 18 09:52:55 OUVS1 kernel: [67330.366039]  [] ? 
kvm_on_user_return+0x6f/0x80 [kvm]
  Mar 18 09:52:55 OUVS1 kernel: [67330.366048]  [] ? 
fire_user_return_notifiers+0x3b/0x50
  Mar 18 09:52:55 OUVS1 kernel: [67330.366070]  [] 
SyS_ioctl+0x79/0x90
  Mar 18 09:52:55 OUVS1 kernel: [67330.366098]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Mar 18 09:52:55 OUVS1 kernel: [67330.366120] ---[ end trace fe86ac8d6b7160d8 
]---
  Mar 18 09:53:23 OUVS1 kernel: [67357.924347] NMI watchdog: BUG: soft lockup - 
CPU#2 stuck for 22s! [qemu-system-x86:5187]
  Mar 18 09:53:23 OUVS1 kernel: [67357.926140] Modules linked in: vhost_net 
vhost macvtap macvlan xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 bridge stp llc xt_TCPMSS xt_tcpmss 
xt_tcpudp iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables pppoe pppox snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic intel_rapl intel_powerclamp 
coretemp punit_atom_debug crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 
lrw gf128mul glue_helper 

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Sorry, I had forgotten my own workaround for this.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: lxc (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Ok, this is happening because lxc, for privileged containers, bind-
mounts /proc/sys and /proc/sys/net onto themselves.  This prevents later
unprivileged mounting of /proc.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Sorry, testcase in #8 is invalid, bc lxc-usernsexec doesn't create a new
pid namespace,  so mount is denied because we do not own our
pidns->userns.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Simplest way to reproduce:

sudo systemctl stop proc-sys-fs-binfmt_misc.automount # (just to be sure)
unshare -mpf
mount --make-rslave /
mount -t proc proc /proc
lxc-usernsexec
# mount -t proc proc /proc # permission denied, regardless what -o options may 
pass.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Current wily kernel is giving me the same behavior.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Upstream kernel still fails:

  lxc-start 20160304193125.498 ERRORlxc_conf - 
conf.c:lxc_mount_auto_mounts:742 - Operation not permitted - error mounting 
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
lxc-start: conf.c: lxc_mount_auto_mounts: 742 Operation not permitted - error 
mounting proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14


Linux x1 4.5.0-999-generic #201603032101 SMP Fri Mar 4 02:03:35 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

Note - I am not actively looking at this bug as I've not managed to
reproduce it.  Hopefully the kernel team has it under control, please
shout if I'm needed.

If using juju first is a prerequisite to reproducing this, I can try
that, but my impression from previous reports has been that this is not
supposed to be a requirement, so I think something else is triggering it
which I'm missing.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

@sforshee,

Because in the past mountall would fail if we didn't.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

@sforshee - are you saying that removing the debugfs line from
/usr/share/lxc/config/ubuntu-common.conf fixes this for you?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

Also cannot reproduce in a clean VM, so I have to assume juju is
tweaking something.

Can you show output of 'lxc config show ' where 
is the container which fails?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

marking confirmed because two people have reported it,  but I cannot
reproduce it yet.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Serge Hallyn]

I'm on the same kernel

Linux sl 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

and also have the tracefs mounted

0 ✓ serge@sl ~ $ grep debug /proc/self/mountinfo
74 19 0:7 / /sys/kernel/debug rw,relatime shared:26 - debugfs debugfs rw
44 74 0:9 / /sys/kernel/debug/tracing rw,relatime shared:29 - tracefs tracefs rw

but trusty (upstart-based) containers start fine for me, using lxc
version 2.0.0~rc4+master~20160229-0647-0ubuntu1~xenial and lxd from git
HEAD.

Very odd therefore that unmounting and re-mounting debugfs works for
you...

Will try in a fresh vm.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551854

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 

[Kernel-packages] [Bug 1539349] Re: sleep from invalid context in aa_move_mount

[Serge Hallyn]

Well, that's wily-proposed, so +1

** Tags removed: verification-needed-wily
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349

Title:
  sleep from invalid context in aa_move_mount

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
  the following policy:

  #include 
  /home/ubuntu/mount {
#include 
#include 

capability,
network,
mount,
/** mkrwixr,
  }

  And then run the following script under sudo from ~/ubuntu:

  #!/bin/sh

  apparmor_parser -r /home/ubuntu/mount.aa
  umount -l a/b
  umount -l a/a
  umount -l a
  rm -rf a
  mkdir a
  mount --bind a a
  mount --make-slave a
  mkdir a/a a/b
  mount -t tmpfs tmpfs a/a
  /home/ubuntu/mount --move a/a a/b

  I get the following kernel warning:

  Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser"
  Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid 
context at mm/slub.c:1287
  Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, 
name: mount
  Jan 29 02:36:06 seth kernel: no locks held by mount/1189.
  Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ 
#4
  Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  Jan 29 02:36:06 seth kernel:   a02414bf 
88007784fc28 81449309
  Jan 29 02:36:06 seth kernel:  880079129580 88007784fc50 
810b5789 81ce0e60
  Jan 29 02:36:06 seth kernel:  0507  
88007784fc78 810b5889
  Jan 29 02:36:06 seth kernel: Call Trace:
  Jan 29 02:36:06 seth kernel:  [] dump_stack+0x4b/0x72
  Jan 29 02:36:06 seth kernel:  [] ___might_sleep+0x179/0x230
  Jan 29 02:36:06 seth kernel:  [] __might_sleep+0x49/0x80
  Jan 29 02:36:06 seth kernel:  [] ? getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] 
kmem_cache_alloc+0x1db/0x2a0
  Jan 29 02:36:06 seth kernel:  [] getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] kern_path+0x16/0x30
  Jan 29 02:36:06 seth kernel:  [] aa_move_mount+0x17c/0x320
  Jan 29 02:36:06 seth kernel:  [] 
apparmor_sb_mount+0x233/0x2d0
  Jan 29 02:36:06 seth kernel:  [] security_sb_mount+0x57/0x80
  Jan 29 02:36:06 seth kernel:  [] do_mount+0xb1/0xe60
  Jan 29 02:36:06 seth kernel:  [] ? __might_fault+0x96/0xa0
  Jan 29 02:36:06 seth kernel:  [] ? memdup_user+0x53/0x80
  Jan 29 02:36:06 seth kernel:  [] SyS_mount+0x9f/0x100
  Jan 29 02:36:06 seth kernel:  [] 
entry_SYSCALL_64_fastpath+0x16/0x76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539349/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1539349] Re: sleep from invalid context in aa_move_mount

[Serge Hallyn]

Wait, that's not a valid test is it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349

Title:
  sleep from invalid context in aa_move_mount

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
  the following policy:

  #include 
  /home/ubuntu/mount {
#include 
#include 

capability,
network,
mount,
/** mkrwixr,
  }

  And then run the following script under sudo from ~/ubuntu:

  #!/bin/sh

  apparmor_parser -r /home/ubuntu/mount.aa
  umount -l a/b
  umount -l a/a
  umount -l a
  rm -rf a
  mkdir a
  mount --bind a a
  mount --make-slave a
  mkdir a/a a/b
  mount -t tmpfs tmpfs a/a
  /home/ubuntu/mount --move a/a a/b

  I get the following kernel warning:

  Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser"
  Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid 
context at mm/slub.c:1287
  Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, 
name: mount
  Jan 29 02:36:06 seth kernel: no locks held by mount/1189.
  Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ 
#4
  Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  Jan 29 02:36:06 seth kernel:   a02414bf 
88007784fc28 81449309
  Jan 29 02:36:06 seth kernel:  880079129580 88007784fc50 
810b5789 81ce0e60
  Jan 29 02:36:06 seth kernel:  0507  
88007784fc78 810b5889
  Jan 29 02:36:06 seth kernel: Call Trace:
  Jan 29 02:36:06 seth kernel:  [] dump_stack+0x4b/0x72
  Jan 29 02:36:06 seth kernel:  [] ___might_sleep+0x179/0x230
  Jan 29 02:36:06 seth kernel:  [] __might_sleep+0x49/0x80
  Jan 29 02:36:06 seth kernel:  [] ? getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] 
kmem_cache_alloc+0x1db/0x2a0
  Jan 29 02:36:06 seth kernel:  [] getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] kern_path+0x16/0x30
  Jan 29 02:36:06 seth kernel:  [] aa_move_mount+0x17c/0x320
  Jan 29 02:36:06 seth kernel:  [] 
apparmor_sb_mount+0x233/0x2d0
  Jan 29 02:36:06 seth kernel:  [] security_sb_mount+0x57/0x80
  Jan 29 02:36:06 seth kernel:  [] do_mount+0xb1/0xe60
  Jan 29 02:36:06 seth kernel:  [] ? __might_fault+0x96/0xa0
  Jan 29 02:36:06 seth kernel:  [] ? memdup_user+0x53/0x80
  Jan 29 02:36:06 seth kernel:  [] SyS_mount+0x9f/0x100
  Jan 29 02:36:06 seth kernel:  [] 
entry_SYSCALL_64_fastpath+0x16/0x76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539349/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1539349] Re: sleep from invalid context in aa_move_mount

[Serge Hallyn]

I get no warnings with  4.2.0-29-generic #34-Ubuntu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349

Title:
  sleep from invalid context in aa_move_mount

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
  the following policy:

  #include 
  /home/ubuntu/mount {
#include 
#include 

capability,
network,
mount,
/** mkrwixr,
  }

  And then run the following script under sudo from ~/ubuntu:

  #!/bin/sh

  apparmor_parser -r /home/ubuntu/mount.aa
  umount -l a/b
  umount -l a/a
  umount -l a
  rm -rf a
  mkdir a
  mount --bind a a
  mount --make-slave a
  mkdir a/a a/b
  mount -t tmpfs tmpfs a/a
  /home/ubuntu/mount --move a/a a/b

  I get the following kernel warning:

  Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser"
  Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid 
context at mm/slub.c:1287
  Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, 
name: mount
  Jan 29 02:36:06 seth kernel: no locks held by mount/1189.
  Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ 
#4
  Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  Jan 29 02:36:06 seth kernel:   a02414bf 
88007784fc28 81449309
  Jan 29 02:36:06 seth kernel:  880079129580 88007784fc50 
810b5789 81ce0e60
  Jan 29 02:36:06 seth kernel:  0507  
88007784fc78 810b5889
  Jan 29 02:36:06 seth kernel: Call Trace:
  Jan 29 02:36:06 seth kernel:  [] dump_stack+0x4b/0x72
  Jan 29 02:36:06 seth kernel:  [] ___might_sleep+0x179/0x230
  Jan 29 02:36:06 seth kernel:  [] __might_sleep+0x49/0x80
  Jan 29 02:36:06 seth kernel:  [] ? getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] 
kmem_cache_alloc+0x1db/0x2a0
  Jan 29 02:36:06 seth kernel:  [] getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] kern_path+0x16/0x30
  Jan 29 02:36:06 seth kernel:  [] aa_move_mount+0x17c/0x320
  Jan 29 02:36:06 seth kernel:  [] 
apparmor_sb_mount+0x233/0x2d0
  Jan 29 02:36:06 seth kernel:  [] security_sb_mount+0x57/0x80
  Jan 29 02:36:06 seth kernel:  [] do_mount+0xb1/0xe60
  Jan 29 02:36:06 seth kernel:  [] ? __might_fault+0x96/0xa0
  Jan 29 02:36:06 seth kernel:  [] ? memdup_user+0x53/0x80
  Jan 29 02:36:06 seth kernel:  [] SyS_mount+0x9f/0x100
  Jan 29 02:36:06 seth kernel:  [] 
entry_SYSCALL_64_fastpath+0x16/0x76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539349/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1546775] [NEW] Please pull cgroup namespaces

[Serge Hallyn]

Public bug reported:

Cgroup namespaces are a new kernel feature which allows virtualizing a
container's /proc/self/cgroups and the root of future cgroupfs mounts,
to make the container appear as though it is in the / cgroup.  This is
one of the pieces needed to be able to run, for instance, docker in a
lxd container.

Cgroup namespaces are implemented by a patchset which is currently in
linux-next.  A patchset ported to the master-next branch of the xenial
kernel tree is at http://people.canonical.com/~serge/patches.v2/

Thank you.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1546775

Title:
  Please pull cgroup namespaces

Status in linux package in Ubuntu:
  New

Bug description:
  Cgroup namespaces are a new kernel feature which allows virtualizing a
  container's /proc/self/cgroups and the root of future cgroupfs mounts,
  to make the container appear as though it is in the / cgroup.  This is
  one of the pieces needed to be able to run, for instance, docker in a
  lxd container.

  Cgroup namespaces are implemented by a patchset which is currently in
  linux-next.  A patchset ported to the master-next branch of the xenial
  kernel tree is at http://people.canonical.com/~serge/patches.v2/

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546775/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

[Serge Hallyn]

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: qemu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-meta-lts-vivid (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1512185

Title:
  qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
  ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-meta-lts-vivid package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
  where qemu-nbd processes would lock up. At the same time, there's also
  a bunch of kernel spew as follows:

  | [605282.018238] block nbd3: Attempted send on closed socket
  | [605282.018242] block nbd3: Attempted send on closed socket
  | [605282.018245] block nbd3: Attempted send on closed socket
  | [605282.018249] block nbd3: Attempted send on closed socket

  swirlix01:

  | hloeung@swirlix01:~$ uname -a
  | Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46 
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
  | hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
  | 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10 
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
  | hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ 
print $1 }')/stack
  | [] __switch_to+0x74/0x8c
  | [] futex_wait_queue_me+0xf4/0x184
  | [] futex_wait+0x154/0x24c
  | [] do_futex+0x1a0/0x9ec
  | [] SyS_futex+0x98/0x1cc
  | [] el0_svc_naked+0x20/0x28
  | [] 0x

  swirlix08:

  | hloeung@swirlix08:~$ uname -a
  | Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
  | hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
  | 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6 
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
  | hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ 
print $1 }')/stack
  | [] __switch_to+0x74/0x8c
  | [] futex_wait_queue_me+0xf4/0x184
  | [] futex_wait+0x154/0x24c
  | [] do_futex+0x1a0/0x9ec
  | [] SyS_futex+0x98/0x1cc
  | [] el0_svc_naked+0x20/0x28
  | [] 0x

  swirlix11:

  | hloeung@swirlix11:~$ uname -a
  | Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
  | hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
  | 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3 
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
  | hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ 
print $1 }'/stack
  | hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ 
print $1 }')/stack
  | [] __switch_to+0x74/0x8c
  | [] futex_wait_queue_me+0xf4/0x184
  | [] futex_wait+0x154/0x24c
  | [] do_futex+0x1a0/0x9ec
  | [] SyS_futex+0x98/0x1cc
  | [] el0_svc_naked+0x20/0x28
  | [] 0x

  | hloeung@swirlix11:~$ sudo strace -f -p 18149
  | Process 18149 attached with 3 threads
  | [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8 
  | [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
  | ... (hangs here) ...

  We're using the QEMU package backported from Vivid as per LP:1457639

  | hloeung@swirlix11:~$ apt-cache policy qemu-utils
  | qemu-utils:
  |   Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
  |   Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
  |   Version table:
  |  *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
  | 500 
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/ 
trusty/main arm64 Packages

  I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 17:42 seq
   crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: qemu (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images trusty uec-images
  Uname: Linux 

Re: [Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

It's not something I regularly do, as I normally nest inside unprivileged
lxd containers.  So I can't say whether it is a regression.  I did revert
to an older trusty kernel and have the same behavior.

I'm going to need to write a script to make this more easily reproducible,
but I won't have time for that today.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] [NEW] nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Public bug reported:

Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
work around other bugs.

Create a privileged container (again either trusty or xenial will do),
and install ubuntu-lxc/daily ppa there.

Create an unprivileged container in that container.  It will fail at
mounting proc using safe_mount.  At this point it is mounting proc onto
/proc/self/fd/14 flags 14.

  lxc-start 20160208234209.189 ERRORlxc_utils -
utils.c:safe_mount:1695 - Operation not permitted - Failed to mount proc
onto /usr/lib/x86_64-linux-gnu/lxc/proc

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: lxc (Ubuntu)
 Importance: High
 Status: Triaged

** Package changed: lxcfs (Ubuntu) => lxc (Ubuntu)

** Changed in: lxc (Ubuntu)
   Importance: Undecided => High

** Changed in: lxc (Ubuntu)
   Status: New => Triaged

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

I'm quite certain this is not an apparmor issue, since leaving
everything unconfined does not help.

It could be something we're doing wrong in lxc, but I'm not sure what.

It could be something inherent in mounting onto an open fd.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1543367] Re: nested unprileged container fails to start at mounting /proc

[Serge Hallyn]

Note that an unprivileged user on the host is able to do these mounts.

Unprivileged users inside a privileged container cannot.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1543367

Title:
  nested unprileged container fails to start at mounting /proc

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  Create a trusty or xenial host.  Probably use ubuntu-lxc/daily ppa to
  work around other bugs.

  Create a privileged container (again either trusty or xenial will do),
  and install ubuntu-lxc/daily ppa there.

  Create an unprivileged container in that container.  It will fail at
  mounting proc using safe_mount.  At this point it is mounting proc
  onto /proc/self/fd/14 flags 14.

lxc-start 20160208234209.189 ERRORlxc_utils -
  utils.c:safe_mount:1695 - Operation not permitted - Failed to mount
  proc onto /usr/lib/x86_64-linux-gnu/lxc/proc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1539349] [NEW] sleep from invalid context in aa_move_mount

[Serge Hallyn]

Public bug reported:

In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
the following policy:

#include 
/home/ubuntu/mount {
  #include 
  #include 

  capability,
  network,
  mount,
  /** mkrwixr,
}

And then run the following script under sudo from ~/ubuntu:

#!/bin/sh

apparmor_parser -r /home/ubuntu/mount.aa
umount -l a/b
umount -l a/a
umount -l a
rm -rf a
mkdir a
mount --bind a a
mount --make-slave a
mkdir a/a a/b
mount -t tmpfs tmpfs a/a
/home/ubuntu/mount --move a/a a/b

I get the following kernel warning:

Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser"
Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid context 
at mm/slub.c:1287
Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, 
name: mount
Jan 29 02:36:06 seth kernel: no locks held by mount/1189.
Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ #4
Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
Jan 29 02:36:06 seth kernel:   a02414bf 
88007784fc28 81449309
Jan 29 02:36:06 seth kernel:  880079129580 88007784fc50 
810b5789 81ce0e60
Jan 29 02:36:06 seth kernel:  0507  
88007784fc78 810b5889
Jan 29 02:36:06 seth kernel: Call Trace:
Jan 29 02:36:06 seth kernel:  [] dump_stack+0x4b/0x72
Jan 29 02:36:06 seth kernel:  [] ___might_sleep+0x179/0x230
Jan 29 02:36:06 seth kernel:  [] __might_sleep+0x49/0x80
Jan 29 02:36:06 seth kernel:  [] ? getname_kernel+0x34/0x120
Jan 29 02:36:06 seth kernel:  [] kmem_cache_alloc+0x1db/0x2a0
Jan 29 02:36:06 seth kernel:  [] getname_kernel+0x34/0x120
Jan 29 02:36:06 seth kernel:  [] kern_path+0x16/0x30
Jan 29 02:36:06 seth kernel:  [] aa_move_mount+0x17c/0x320
Jan 29 02:36:06 seth kernel:  [] apparmor_sb_mount+0x233/0x2d0
Jan 29 02:36:06 seth kernel:  [] security_sb_mount+0x57/0x80
Jan 29 02:36:06 seth kernel:  [] do_mount+0xb1/0xe60
Jan 29 02:36:06 seth kernel:  [] ? __might_fault+0x96/0xa0
Jan 29 02:36:06 seth kernel:  [] ? memdup_user+0x53/0x80
Jan 29 02:36:06 seth kernel:  [] SyS_mount+0x9f/0x100
Jan 29 02:36:06 seth kernel:  [] 
entry_SYSCALL_64_fastpath+0x16/0x76

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1539349

Title:
  sleep from invalid context in aa_move_mount

Status in linux package in Ubuntu:
  New

Bug description:
  In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define
  the following policy:

  #include 
  /home/ubuntu/mount {
#include 
#include 

capability,
network,
mount,
/** mkrwixr,
  }

  And then run the following script under sudo from ~/ubuntu:

  #!/bin/sh

  apparmor_parser -r /home/ubuntu/mount.aa
  umount -l a/b
  umount -l a/a
  umount -l a
  rm -rf a
  mkdir a
  mount --bind a a
  mount --make-slave a
  mkdir a/a a/b
  mount -t tmpfs tmpfs a/a
  /home/ubuntu/mount --move a/a a/b

  I get the following kernel warning:

  Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser"
  Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid 
context at mm/slub.c:1287
  Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, 
name: mount
  Jan 29 02:36:06 seth kernel: no locks held by mount/1189.
  Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ 
#4
  Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  Jan 29 02:36:06 seth kernel:   a02414bf 
88007784fc28 81449309
  Jan 29 02:36:06 seth kernel:  880079129580 88007784fc50 
810b5789 81ce0e60
  Jan 29 02:36:06 seth kernel:  0507  
88007784fc78 810b5889
  Jan 29 02:36:06 seth kernel: Call Trace:
  Jan 29 02:36:06 seth kernel:  [] dump_stack+0x4b/0x72
  Jan 29 02:36:06 seth kernel:  [] ___might_sleep+0x179/0x230
  Jan 29 02:36:06 seth kernel:  [] __might_sleep+0x49/0x80
  Jan 29 02:36:06 seth kernel:  [] ? getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] 
kmem_cache_alloc+0x1db/0x2a0
  Jan 29 02:36:06 seth kernel:  [] getname_kernel+0x34/0x120
  Jan 29 02:36:06 seth kernel:  [] kern_path+0x16/0x30
  Jan 29 02:36:06 seth kernel:  [] aa_move_mount+0x17c/0x320
  Jan 29 02:36:06 seth kernel:  [] 
apparmor_sb_mount+0x233/0x2d0
  Jan 29 02:36:06 seth kernel:  [] security_sb_mount+0x57/0x80
  Jan 29 02:36:06 seth kernel:  [] do_mount+0xb1/0xe60
  Jan 29 02:36:06 seth 

[Kernel-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Serge Hallyn]

** Changed in: cgmanager (Ubuntu)
   Status: Confirmed => Fix Released

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1392176

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1536280] Re: domain shutdown fails for libvirt/lxc

[Serge Hallyn]

marking as affecting kernel given the description.


** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536280

Title:
  domain shutdown fails for libvirt/lxc

Status in libvirt package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There appears to be a regression from kernel 3.13.0-58-generic where
  virDomainShutdown no longer brings the domain to shutoff state in
  newer Ubuntu kernels.

  Details:
  

  OS:
  ---
  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Kernel:
  ---
  $ uname -a
  Linux thomas-devstack01 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:59:10 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Package:
  
  $ dpkg -l | grep libvirt-bin
  ii  libvirt-bin  1.2.2-0ubuntu13.1.16 
 amd64programs for the libvirt library

  Libvirt virt driver: LXC

  Issue seen from console:
  

  $ sudo virsh -c lxc:/// shutdown instance-0001
  error: Failed to shutdown domain instance-0001
  error: internal error: Child process (1304) unexpected exit status 1

  libvirtd logs:
  --

  2016-01-20 16:42:38.267+: 14089: debug : virDomainShutdown:3094 : 
dom=0x7f89d0004a70, (VM: name=instance-0001, 
uuid=e342beb8-8666-4a47-8b40-5844e866e1f7)
  2016-01-20 16:42:38.269+: 14089: error : virProcessWait:191 : internal 
error: Child process (1304) unexpected exit status 1

  nova-compute logs
  -
  *Note*: From when attempting to do a nova stop  in devstack

  
  2016-01-20 16:37:35.244 ERROR oslo_messaging.rpc.dispatcher 
[req-dd0fe69c-9bd2-4de5-b59b-77619699d69b demo demo] Exception during message 
handling: internal error: Child process
  (631) unexpected exit status 1
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 357, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 330, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 407, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 385, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 

Re: [Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

> Something I'm still not sure about is what would happen if you made a
> symlink, bind mount, etc. in upperdir with the same name as an unrelated
> file in lowerdir. This is worth checking out.

just tried a symlink and it didn't seem to affect the host directory
(/opt/cisco) which was symlinked to /tmp/upper/cisco in the container to
begin with.

> > It looks like no, since
> > 
> > root@w1:/tmp# mount -t overlay -o 
> > lowerdir=lower,upperdir=upper,workdir=workdir overlay /mnt
> > root@w1:/tmp# ls /mnt
> > cisco
> > root@w1:/tmp# rmdir /mnt/cisco
> > rmdir: failed to remove ‘/mnt/cisco’: Read-only file system
> > root@w1:/tmp# mv /mnt/cisco /mnt/c2
> > mv: cannot move ‘/mnt/cisco’ to ‘/mnt/c2’: Read-only file system
> > 
> > (here w1 is a unpriv container with /hostopt a bind mount of /opt on the
> > host;  cisco a directory both in host's /opt and in /tmp/lowerdir)
> 
> I think I'm missing something here. I don't know why your mount is
> read-only.

Because a directory in workdir is owned by uid -1 (root on the host).

> But even if it wasn't, cisco is in lowerdir and thus should
> never be modified or removed in any case. Removing it in /mnt should (I

Right, but I was trying to use workdir as a vector to make changes to
something in the host's opt.  Not lowerdir.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

Does it require the workdir to be empty?

I.e. is there a way (symlink, bind mount, something else) that a user
could use a dir they own which has a child which they don't own?

It looks like no, since

root@w1:/tmp# mount -t overlay -o lowerdir=lower,upperdir=upper,workdir=workdir 
overlay /mnt
root@w1:/tmp# ls /mnt
cisco
root@w1:/tmp# rmdir /mnt/cisco
rmdir: failed to remove ‘/mnt/cisco’: Read-only file system
root@w1:/tmp# mv /mnt/cisco /mnt/c2
mv: cannot move ‘/mnt/cisco’ to ‘/mnt/c2’: Read-only file system

(here w1 is a unpriv container with /hostopt a bind mount of /opt on the
host;  cisco a directory both in host's /opt and in /tmp/lowerdir)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

Quoting Seth Forshee (seth.forshee...@canonical.com):
> I don't know why #2 is that much grosser than what's there now. It's

I didn't mean gross as in eeuw, I meant not fine-grained enough.

Because the capability will apply to inode permissions checks,
and we only want it to be used for the check authorizing the
writing of the trusted.overlay.opaque xattr.

> already only taking the cap for setting the xattr, and taking
> CAP_SYS_ADMIN in init_user_ns seems to be what it's really wanting to do

Maybe - that's what I'm not sure about.  As you said earlier, in the
upstream code only an admin can do the actual mount.  The fact that an
unpriv user can create the mount may change assumptions about the
underlying fs's.

> there. The difference now though is that before that capability would
> have been required to do the mount and now it isn't.

Right.

> If we were to use ns_capable, which namespace do we use?

I don't know.  We're almost better off shipping a new version of
vfs_xattr() which is only for use by kernel writers.

If we had your patch we could maybe check against the sb->user_ns?

> current_user_ns? Then that check becomes worthless because any user can
> make a new namespace to bypass it. If we had the s_user_ns patches it

Quit saying in the next paragraph what I say in reply to the previous!

> might make sense to use that, but that probably doesn't solve the
> problem anyway since the lower mount was probably mounted in
> init_user_ns.

Good point, hadn't thought of that.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

in ovl_clear_empty(), the opaque bit is set on the dir in workingdir

in ovl_create_over_whiteout() (the case we're currently looking at) it is
also being set in the working dir.

in ovl_rename2(), it is set in two places, on the upper dentries for
both the old and new.

So it is never set on the lowerdir, at least.

I'm still looking, but it may be safe to say that all needed inode
checks are already done before we call ovl_set_opaque() so that we
can indeed just use prepare_kernel_cred(NULL) instead of prepare_cred().

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

#2 is probably a bit too gross - we really only need the cap for the setting
of the OVL_XATTR_OPAQUE xattr in ovl_set_opaque.  So we could simply override
creds again there.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

hat may not be ok for the ovl_rename2 case.

What we want is for inode permissions to be checked, but only the
bit in xattr_permission() checking for trusted.* to accept ns_capable.

We could special-case that in xattr_permission(), but that's not
particularly nice.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

Ok, I see.  At one point we had a special case to allow the overlay code
to write trusted.* xattrs for creating whiteouts.

However that is gone.  Therefore when overlayfs v1 (mount -t overlayfs)
is mounted, root in a user namespace also is not able to rm a file which
exists in the lower fs.

Some ways to fix this:

1. Add a special case in fs/xattr.c to allow the overlay code to create the 
trusted.overlay xattrs
2. In ovl_create_or_link(), target the override cred at init_user_ns.  Since we 
don't do that, the capabilities we are adding do not grant 
"capable(CAP_SYS_ADMIN)", only ns_capable.
3. Find another way to do this without requiring the trusted.overlay xattr.  It 
isn't needed for files so I don't know what the complications are, which 
require it to be done for directories.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

The type of the underlaying file does not matter, only the type of the
replacing object.

So if you

touch $t/dev; rm $t/dev; touch $t/dev
mkdir $t/dev; rmdir $t/ev; touch $t/dev

those succeed, while

touch $t/dev; rm $t/dev; mkdir $t/dev
mkdir $t/dev; rm $t/dev; mkdir $t/dev


both fail.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

In ovl_create_over_whiteout(), the ovl_set_opaque() in the S_ISDIR()
block failed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir

[Serge Hallyn]

summary  overlay: mkdir in user namespace fails if directory exists in
lowerdir"


** Description changed:

  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).
  
  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
-   umount -l $dir/t
-   rm -rf $dir
+  umount -l $dir/t
+  rm -rf $dir
  }
  
  trap cleanup EXIT
  
  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =
+ 
+ The above will work on the host, but fail in a user namespace, i.e
+ in a regular lxd container.

** Summary changed:

- overlay: mkdir fails if directory exists in lowerdir
+ overlay: mkdir fails if directory exists in lowerdir in a user namespace

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Serge Hallyn]

Quoting Joseph Salisbury (joseph.salisb...@canonical.com):
> Can you see if this bug also happens with the latest mainline kernel?  It can 
> be downloaded from:

That is not an option, because the mainline kernel doesn't support unprivileged
overlayfs mounting which is where this happens.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Serge Hallyn]

@Sqxm - thanks for that input.

For what it's worth you should be able to use ppa:serge-hallyn/systemd
in xenial to get cpusets not created by default.  Unfortunately I need
to make some more changes (in particular to use the systemd-created
cgroups when they exist) before pushing this to the archive.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1392176

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp