[Kernel-packages] [Bug 1703742] [NEW] Transparent hugepages should default to enabled=madvise

2017-07-11 Thread Nelson Elhage
Public bug reported:

Ubuntu kernels should default transparent_hugepages to enabled=madvise,
not enabled=always

(this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config).

I've blogged about this at some length here:
https://blog.nelhage.com/post/transparent-hugepages/ but here is a
summary:

Transparent Hugepages are a feature that allows the kernel to attempt to
automatically back any anonymous maps with "huge" 2MiB page tables,
instead of the normal 4k entries. It can produce small net performance
gains in certain benchmarks, but also has numerous downsides, in the
form of apparent memory leaks and 30% slowdowns or worse for some
applications. Many popular pieces of software now refuse to run with
hugepages enabled because of known performance issues.

Examples of problem reports:
MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/
Oracle: 
https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge
Splunk: 
https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP
Go runtime: https://github.com/golang/go/issues/8832
jemalloc: 
https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/
node.js: https://github.com/nodejs/node/issues/11077

Setting `enabled=madvise` enables applications that know they benefit
from transparent huge pages to opt-in to this feature, while eliminating
all the problematic behavior for other applications. Note also that
transparent hugepage settings don't affect the use of explicit hugepages
via hugetlbfs or mmap(…, MAP_HUGETLB, …)

** 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/1703742

Title:
  Transparent hugepages should default to enabled=madvise

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu kernels should default transparent_hugepages to
  enabled=madvise, not enabled=always

  (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config).

  I've blogged about this at some length here:
  https://blog.nelhage.com/post/transparent-hugepages/ but here is a
  summary:

  Transparent Hugepages are a feature that allows the kernel to attempt
  to automatically back any anonymous maps with "huge" 2MiB page tables,
  instead of the normal 4k entries. It can produce small net performance
  gains in certain benchmarks, but also has numerous downsides, in the
  form of apparent memory leaks and 30% slowdowns or worse for some
  applications. Many popular pieces of software now refuse to run with
  hugepages enabled because of known performance issues.

  Examples of problem reports:
  MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/
  Oracle: 
https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge
  Splunk: 
https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP
  Go runtime: https://github.com/golang/go/issues/8832
  jemalloc: 
https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/
  node.js: https://github.com/nodejs/node/issues/11077

  Setting `enabled=madvise` enables applications that know they benefit
  from transparent huge pages to opt-in to this feature, while
  eliminating all the problematic behavior for other applications. Note
  also that transparent hugepage settings don't affect the use of
  explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+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 1547231] Re: /proc/$pid/maps performance regression

2016-03-29 Thread Nelson Elhage
These patches have landed in v4.5rc3 squashed as
65376df582174ffcec9e6471bf5b0dd79ba05e4a (v4.5-rc3~15^2~9). Is that
sufficient, or should I reping once 4.5 final is out?

-- 
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/1547231

Title:
  /proc/$pid/maps performance regression

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged

Bug description:
  /proc/$pid/maps experienced a significant performance regression for
  processes with large numbers of threads between Precise and Trusty due
  to an upstream bug. This behavior is currently blocking my ability to
  upgrade to Trusty, as we depend on applications with with 10s of
  thousands of threads.

  The issue has been fixed in the usptream -mm tree.

  Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712
  Upstream patches:
  
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=2d2a106c79f4b5b2b10e72957f7448e276dbf0a9
  
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=eb1899e03405faf7c79396ae9593303d53e2710d

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 18 12:13 seq
   crw-rw 1 root audio 116, 33 Feb 18 12:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  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:
  Date: Thu Feb 18 13:44:23 2016
  MachineType: Supermicro A1SAi
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A1SAi
  dmi.board.vendor: Supermicro
  dmi.board.version: 123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 18
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd02/27/2014:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SAi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.:
  dmi.product.name: A1SAi
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547231/+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 1547231] [NEW] /proc/$pid/maps performance regression

2016-02-18 Thread Nelson Elhage
Public bug reported:

/proc/$pid/maps experienced a significant performance regression for
processes with large numbers of threads between Precise and Trusty due
to an upstream bug. This behavior is currently blocking my ability to
upgrade to Trusty, as we depend on applications with with 10s of
thousands of threads.

The issue has been fixed in the usptream -mm tree.

Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712
Upstream patches:
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=2d2a106c79f4b5b2b10e72957f7448e276dbf0a9
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=eb1899e03405faf7c79396ae9593303d53e2710d

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-36-generic 3.13.0-36.63
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 18 12:13 seq
 crw-rw 1 root audio 116, 33 Feb 18 12:13 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.19
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:
Date: Thu Feb 18 13:44:23 2016
MachineType: Supermicro A1SAi
PciMultimedia:
 
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-36-generic N/A
 linux-backports-modules-3.13.0-36-generic  N/A
 linux-firmware 1.127.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago)
WifiSyslog:
 
dmi.bios.date: 02/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A1SAi
dmi.board.vendor: Supermicro
dmi.board.version: 123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 18
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd02/27/2014:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SAi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.:
dmi.product.name: A1SAi
dmi.product.version: 123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug trusty

-- 
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/1547231

Title:
  /proc/$pid/maps performance regression

Status in linux package in Ubuntu:
  New

Bug description:
  /proc/$pid/maps experienced a significant performance regression for
  processes with large numbers of threads between Precise and Trusty due
  to an upstream bug. This behavior is currently blocking my ability to
  upgrade to Trusty, as we depend on applications with with 10s of
  thousands of threads.

  The issue has been fixed in the usptream -mm tree.

  Upstream report: http://comments.gmane.org/gmane.linux.kernel.mm/144712
  Upstream patches:
  
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=2d2a106c79f4b5b2b10e72957f7448e276dbf0a9
  
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/?h=since-4.4&id=eb1899e03405faf7c79396ae9593303d53e2710d

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 18 12:13 seq
   crw-rw 1 root audio 116, 33 Feb 18 12:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  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:
  Date: Thu Feb 18 13:44:23 2016
  MachineType: Supermicro A1SAi
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=/dev/md1 ro console=tty0 console=ttyS0,57600
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-18 (579 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: Am

[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage

2016-01-19 Thread Nelson Elhage
One more note to anyone else trying to debug this: I can reproduce quite
reliably by copying a 3GiB file from S3 onto a gp2 EBS volume using `aws
s3 cp`.

-- 
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/1518457

Title:
  kswapd0 100% CPU usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+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 1518457] Re: kswapd0 100% CPU usage

2016-01-17 Thread Nelson Elhage
Some further debugging: On my t2.micro test case, the machine comes up
with 9 memory devices, the last of which is offline at boot. Bringing
that device online by hand (with the udev rules disabled) triggers the
bug.

# echo online > /sys/devices/system/memory/memory8/state

So something about bringing that node online causes the problem. The
udev bugfix causes udev to automatically bring it up, which is why that
introduced the issue, but it doesn't seem like udev is really the root
problem here.

-- 
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/1518457

Title:
  kswapd0 100% CPU usage

Status in linux package in Ubuntu:
  In Progress

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+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 1518457] Re: kswapd0 100% CPU usage

2016-01-17 Thread Nelson Elhage
I did some experimentation, and I can reproduce @oystein-gisnas's result
that nuking that file from `/lib/udev/rules.d/` and rebooting fixes the
issue.

However, removing that file and restarting udev does *not* seem to fix
the issue. So I suspect the problem is not with udev, but rather with
some kernel feature that udev is enabling or toggling as part of
processing that file.

Also, as an aside, editing that file isn't a good workaround, since
upgrading udev may clobber it again. If you instead create an
`/etc/udev/rules.d/40-vm-hotadd.rules`  containing the edited version,
that file will take precedence over the one in `/lib`, and also be
robust against udev upgrades.

-- 
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/1518457

Title:
  kswapd0 100% CPU usage

Status in linux package in Ubuntu:
  In Progress

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+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 1445664] Re: kernel 3.16 breaks POSIX extended ACLs over NFS

2015-12-24 Thread Nelson Elhage
I may or may not have time to do the bisect any time soon, but based on
some log-diving, I strongly suspect
https://github.com/torvalds/linux/commit/013cdf1088d7235da9477a2375654921d9b9ba9f
or the related refactors of being the commit that introduced this
regression.

-- 
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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] Re: kernel 3.16 breaks POSIX extended ACLs over NFS

2015-12-22 Thread Nelson Elhage
Reproduced on

$ uname -a
Linux packer-vmware-iso 4.4.0-040400rc6-generic #201512202030 SMP Mon Dec 21 
01:32:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.4-rc6

-- 
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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] UdevLog.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539017/+files/UdevLog.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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] WifiSyslog.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539018/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] UdevDb.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1445664/+attachment/4539016/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] ProcModules.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539015/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] ProcInterrupts.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539014/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] ProcCpuinfo.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539012/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] Lspci.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1445664/+attachment/4539011/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] ProcEnviron.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539013/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] CurrentDmesg.txt

2015-12-22 Thread Nelson Elhage
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539010/+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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
   crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
  InstallationDate: Installed on 2015-09-02 (111 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  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/20/2014: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/1445664/+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 1445664] Re: kernel 3.16 breaks POSIX extended ACLs over NFS

2015-12-22 Thread Nelson Elhage
apport information

** Tags added: apport-collected trusty

** Description changed:

  I have a development environment that uses Vagrant with NFS shares to a
  Trusty development VM from OS X laptops.
  
  After the upgrade to the HWE kernel 3.16, installing Ruby gems into the
  NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".
  
  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even hits
  the NFS layer, it passes through a generic permission-check layer. It
  appears that that layer is not aware of NFS UID remapping, and so fails
  the call regardless of what the server would have done.
  
  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.
  
  The broken system is:
  
  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Dec 22 14:39 seq
+  crw-rw 1 root audio 116, 33 Dec 22 14:39 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ 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
+ HibernationDevice: RESUME=/dev/mapper/packer--vmware--iso--vg-swap_1
+ InstallationDate: Installed on 2015-09-02 (111 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/packer--vmware--iso--vg-root ro quiet
+ ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
+ RelatedPackageVersions:
+  linux-restricted-modules-3.16.0-57-generic N/A
+  linux-backports-modules-3.16.0-57-generic  N/A
+  linux-firmware 1.127.15
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  trusty
+ Uname: Linux 3.16.0-57-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/20/2014
+ 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/20/2014: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: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1445664/+attachment/4539009/+files/BootDmesg.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/1445664

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless o

[Kernel-packages] [Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2015-12-04 Thread Nelson Elhage
** Attachment added: "/proc/zoneinfo from the same machine"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+attachment/4529727/+files/zoneinfo.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/1497428

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+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 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2015-12-04 Thread Nelson Elhage
Hi @ddstreet, thanks for the update.

We unfortunately weren't able to reproduce this on your test kernel, and
have since moved to a newer kernel version for other reasons.

However, I can confirm that on the affected machine types, and only the
affected machine type, we see a memory range in `/proc/iomem` that ends
off of a multiple of 2M. Again, we do not see this on any other
machines.

I've attached `/proc/iomem` and `/proc/zoneinfo` from an affected machine 
(currently running an LTS backport kernel:
Linux [redacted] 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
)

I'm pretty sure they show the kind of mismatch you're talking about;
iomem shows

1-f0fffefff : System RAM
f0000-f0fff : RAM buffer
f1000-f17ff : System RAM


But the “Node 0 Normal” zone, judging from (start_pfn, start_pfn+spanned) spans 
1-f1800. The machine in question is a c4.8xlarge in EC2.
 


** Attachment added: "iomem.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+attachment/4529726/+files/iomem.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/1497428

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+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 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2015-11-06 Thread Nelson Elhage
Hey,

We're also seeing this issue on a production system, and have been
around 1/week for a while now. We may be able to boot that test kernel
for experimentation purposes – would that still be useful?

-- 
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/1497428

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+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 1445664] [NEW] kernel 3.16 breaks POSIX extended ACLs over NFS

2015-04-17 Thread Nelson Elhage
Public bug reported:

I have a development environment that uses Vagrant with NFS shares to a
Trusty development VM from OS X laptops.

After the upgrade to the HWE kernel 3.16, installing Ruby gems into the
NFS mount inside the VM failed because of install(1) failing with
permission errors. Debugging revealed that it's trying to set POSIX
extended ACLs using setxattr(); On 3.13 this operation failed with
EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
fails with EPERM, even if the NFS mount is explicitly mounted with
"noacl".

Debugging with ftrace and source diving suggests that kernel 3.16
refactored the POSIX extended ACL code so that before the call even hits
the NFS layer, it passes through a generic permission-check layer. It
appears that that layer is not aware of NFS UID remapping, and so fails
the call regardless of what the server would have done.

A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

The broken system is:

vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename:   trusty
Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1445664/+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 1445664] Re: kernel 3.16 breaks POSIX extended ACLs over NFS

2015-04-17 Thread Nelson Elhage
To be clear, I can easily workaround in my environment by not using the
HWE kernel (there's no need for it inside a VM), but this is still a
regression that may affect other people and presumably future Ubuntu
releases.

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

Title:
  kernel 3.16 breaks POSIX extended ACLs over NFS

Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  I have a development environment that uses Vagrant with NFS shares to
  a Trusty development VM from OS X laptops.

  After the upgrade to the HWE kernel 3.16, installing Ruby gems into
  the NFS mount inside the VM failed because of install(1) failing with
  permission errors. Debugging revealed that it's trying to set POSIX
  extended ACLs using setxattr(); On 3.13 this operation failed with
  EOPNOTSUPP (the server does not support extended ACLs), but on 3.16 it
  fails with EPERM, even if the NFS mount is explicitly mounted with
  "noacl".

  Debugging with ftrace and source diving suggests that kernel 3.16
  refactored the POSIX extended ACL code so that before the call even
  hits the NFS layer, it passes through a generic permission-check
  layer. It appears that that layer is not aware of NFS UID remapping,
  and so fails the call regardless of what the server would have done.

  A simple test case is `install -c -m 0755  `, which will succeed on 3.13 and fail on 3.16.

  The broken system is:

  vagrant@packer-vmware-iso:~$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  Codename:   trusty
  Linux packer-vmware-iso 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 
17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1445664/+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