[Kernel-packages] [Bug 1661699] [NEW] linux: 3.19.0-81.89 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 3.19.0-81.89 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-vivid kernel-release-tracking-bug vivid

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-vivid

** Tags added: vivid

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

[Kernel-packages] [Bug 1660704] Re: linux: 4.4.0-63.84 -proposed tracker

[Thadeu Lima de Souza Cascardo]

This was an accidental removal of the control.d/transitionals-lts file.
A patch has already been sent for review.

Thanks for noticing.
Cascardo.

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

Title:
  linux: 4.4.0-63.84 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-63.84 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1660704/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-meta-snapdragon package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-meta-snapdragon source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-meta-snapdragon source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Confirmed
Status in linux-meta-snapdragon source package in Xenial:
  In Progress
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-meta (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Confirmed
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1649718] Re: Linux rtc self test fails in a VM under xenial

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Linux rtc self test fails in a VM under xenial

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

Bug description:
  == SRU Justification ==

  Impact: A race in kvm can result in the EOI signal for the rtc irq to
  be lost. After this happens no more rtc interrupts will be delivered
  to the guest.

  Fix: Three upstream cherry picks which fix the problem.

  Regression Potential: These patches have been upstream since 4.6, so
  they're well-tested at this point. Thus regressions are unlikely.

  ---

  ADT testing for the linux package hangs at the kernel's rtc selftest,
  for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/linux/20161212_132117_a258d@/log.gz

  Running this test manually, I've observed that this will hang in me
  with various kernel versions going back to 4.4 in a VM on my machine
  which is running xenial. The test runs to completion in a VM on a
  different machine running zesty.

  This is the section of the test which produces the hang:

  /* Turn on update interrupts (one per second) */
  retval = ioctl(fd, RTC_UIE_ON, 0);
  if (retval == -1) {
  if (errno == EINVAL) {
  fprintf(stderr,
  "\n...Update IRQs not supported.\n");
  goto test_READ;
  }
  perror("RTC_UIE_ON ioctl");
  exit(errno);
  }

  fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
  rtc);
  fflush(stderr);
  for (i=1; i<6; i++) {
  /* This read will block */
  retval = read(fd, , sizeof(unsigned long));
  if (retval == -1) {
  perror("read");
  exit(errno);
  }
  fprintf(stderr, " %d",i);
  fflush(stderr);
  irqcount++;
  }

  The read blocks indefinitely most of the time. After boot it might
  return once or twice before it hangs, but running the test
  subsequently always hangs on the first read. I'll attach the full
  source for the test (rtctest.c).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649718/+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 1660704] [NEW] linux: 4.4.0-63.84 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 4.4.0-63.84 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-xenial

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: 

[Kernel-packages] [Bug 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running
  ping will stop working

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

Bug description:
  ---Problem Description---
  If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing 
something like a ping flood. The PF interface will stop pinging. 
  We found a small window were MMIO are bein g disabled during pci_enable_sriov 
is called. 
   
  ---uname output---
  4.4.0-30-generic
   
  ---Additional Hardware Info---
  It needs a Mellanox CX4 SRIOV capable to recreate this issue 

  Machine Type = P8 

  ---Steps to Reproduce---
   just configure the IP address of PF interface and start like a ping flood to 
that interface.
  then do this echo to enable SRIOV on the PF. 
  echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs
  Then you will notice the ping flood will stop. 
   
  A patch that will fix this issue was sent for review:
  https://patchwork.ozlabs.org/patch/671517/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: linux-meta-aws (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-meta-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-aws package in Ubuntu:
  New
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-meta-snapdragon package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-aws source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-meta-snapdragon source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-aws source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-meta-snapdragon source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-aws source package in Xenial:
  In Progress
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Fix Committed
Status in linux-meta-snapdragon source package in Xenial:
  Fix Committed
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1660704] Re: linux: 4.4.0-63.84 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1660704

Title:
  linux: 4.4.0-63.84 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-63.84 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1660704/+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 1662705] Re: linux-ti-omap4: 3.2.0-1500.127 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux-ti-omap4:  -proposed tracker
+ linux-ti-omap4: 3.2.0-1500.127 -proposed tracker

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

Title:
  linux-ti-omap4: 3.2.0-1500.127 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1662192
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1662705/+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 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running
  ping will stop working

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

Bug description:
  ---Problem Description---
  If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing 
something like a ping flood. The PF interface will stop pinging. 
  We found a small window were MMIO are bein g disabled during pci_enable_sriov 
is called. 
   
  ---uname output---
  4.4.0-30-generic
   
  ---Additional Hardware Info---
  It needs a Mellanox CX4 SRIOV capable to recreate this issue 

  Machine Type = P8 

  ---Steps to Reproduce---
   just configure the IP address of PF interface and start like a ping flood to 
that interface.
  then do this echo to enable SRIOV on the PF. 
  echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs
  Then you will notice the ping flood will stop. 
   
  A patch that will fix this issue was sent for review:
  https://patchwork.ozlabs.org/patch/671517/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+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 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  Backport Dirty COW patch to prevent wineserver freeze

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+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 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

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

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1661232] [NEW] linux: 4.8.0-38.40 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 4.8.0-38.40 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed block-proposed-yakkety kernel-release-tracking-bug 
yakkety

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

** Tags added: block-proposed-yakkety

** Tags added: yakkety

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: 

[Kernel-packages] [Bug 1661232] Re: linux: 4.8.0-38.40 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Description changed:

  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ -- swm properties --
+ derivative-trackers-created: true

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

Title:
  linux: 4.8.0-38.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1661232/+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 1660704] Re: linux: 4.4.0-63.84 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: Invalid => Confirmed

** Changed in: kernel-sru-workflow/upload-to-ppa
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: Confirmed => In Progress

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

Title:
  linux: 4.4.0-63.84 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-63.84 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1660704/+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 1662186] [NEW] linux: 3.13.0-109.156 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 3.13.0-109.156 upload package. This bug
will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team 

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

Hi, Luk.

linux-image-4.8.0-34-generic should not be affected by this. If you see
unexpected OOM problems, please open a new bug report and attach the
kernel logs, please.

Thanks.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

This is fixed in 4.4.0-63.84, which will be available in proposed soon.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+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 1661232] Re: linux: 4.8.0-38.40 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/upload-to-ppa
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

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

Title:
  linux: 4.8.0-38.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1661232/+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 1661232] Packages available

[Thadeu Lima de Souza Cascardo]

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-raspi2 - bug 1661651

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-hwe-edge (16.04.1) - bug 1661654

It was not possible to create or handle the tracking bugs for the following 
packages (their tracking bugs based on this update must be handled manually):
linux-hwe (16.04.1)

** Description changed:

  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ derivative-trackers-created: true
  phase: Packaging

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

Title:
  linux: 4.8.0-38.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1661232/+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 1661232] Re: linux: 4.8.0-38.40 -proposed tracker

[Thadeu Lima de Souza Cascardo]

-- swm properties --
derivative-trackers-created: false

** Description changed:

  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- derivative-trackers-created: true
  phase: Packaging

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

Title:
  linux: 4.8.0-38.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.8.0-38.40 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1661232/+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 1659381] [NEW] linux: 4.8.0-37.39 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 4.8.0-37.39 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

kernel-stable-phase-changed:Wednesday, 25. January 2017 18:17 UTC
kernel-stable-phase:Packaging

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed block-proposed-yakkety kernel-release-tracking-bug 
yakkety

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

** Tags added: block-proposed-yakkety

** Tags added: yakkety

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: 

[Kernel-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  Mouse cursor invisible or does not move

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646574/+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 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial

[Thadeu Lima de Souza Cascardo]

I built the attached patch and put the binaries at [1].

It would be nice to have someone test it before we push it for review
and maybe respin.

[1] http://people.canonical.com/~cascardo/lp1658999/

** Patch added: 
"0001-UBUNTU-SAUCE-i915_bpo-change-WARN_ON-wm_changed-to-n.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658999/+attachment/4809051/+files/0001-UBUNTU-SAUCE-i915_bpo-change-WARN_ON-wm_changed-to-n.patch

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

Title:
  [Xenial Regression] Kernel panics on HDMI in Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a
  wide range of displays.  He's running 4.4.0-62.83 and notes this is 
definitely a regression as it was working previously.

  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995791] [
  cut here ]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995842] WARNING: CPU: 4
  PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675
  skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995846] WARN_ON(!wm_changed)
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995849] Modules linked
  in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay
  aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE
  nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4
  nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep
  binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek
  snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO)
  spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel
  snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi
  brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl
  x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp
  crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel
  uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw
  videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl
  glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152
  v4l2_common hid_multitouch mii videodev snd media joydev input_leds
  serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device
  shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss
  hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800
  intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap
  int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf
  industrialio kvm_intel kvm irqbypass iptable_filter ip_tables
  ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4
  usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm
  i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt
  fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi
  pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996021] CPU: 4 PID: 2548
  Comm: Xorg Tainted: P   O4.4.0-62-generic #83-Ubuntu
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996024] Hardware name:
  Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996027]
  0286 5b61ce69 880880293920 813f7c63
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996033]
  880880293968 c02be9a0 880880293958 810812d2
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996037]
  88089255f000 88089160a148 88089255e000 880892644b78
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996042] Call Trace:
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996051]
  [] dump_stack+0x63/0x90
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996059]
  [] warn_slowpath_common+0x82/0xc0
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996064]
  [] warn_slowpath_fmt+0x5c/0x80
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996101]
  [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996136]
  [] skl_update_wm+0x185/0x610 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996190]
  [] ? intel_ddi_enable_transcoder_func+0x17f/0x260
  [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996225]
  [] intel_update_watermarks+0x1e/0x30 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996276]
  [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996327]
  [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996366]
  [] ? drm_atomic_check_only+0x18e/0x590 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996397]
  [] drm_atomic_commit+0x37/0x60 [drm]
  Jan 24 

[Kernel-packages] [Bug 1666905] [NEW] linux: 3.13.0-111.158 -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This bug is for tracking the 3.13.0-111.158 upload package. This bug
will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

kernel-stable-phase-changed:Wednesday, 22. February 2017 14:01 UTC
kernel-stable-phase:Packaging

-- swm properties --
derivative-trackers-created: true
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/kernel-snap-beta
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/kernel-snap-candidate
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/kernel-snap-edge
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/kernel-snap-stable
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/kernel-snap-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/kernel-snap-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/kernel-snap-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/kernel-snap-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1660519] Re: Windows guest got 0x5c BSOD when rebooting

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Windows guest got 0x5c BSOD when rebooting

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

Bug description:
  [Impact]

  When rebooting Windows guest, it gets 0x5c BSOD
  Impact to 3.13 ( trusty )
  no Impact to 4.x

  [Fix]

  Upstream development
  4114c27d450bef228be9c7b0c40a888e18a3a636
  ("KVM: x86: reset RVI upon system reset")
  6d2a0526b09e551d0f395cfb63e7cb965db825af
  ("KVM: x86: Emulator should set DR6 upon GD like real CPU")

  and got one MACRO definition from below commit as 6d2a05's dependency
  6f43ed01e87c8a8dbd8c826eaf0f714c1342c039
  (whole 6f43ed commit has a lot of dependency to the other commits)

  [Testcase]

  Running 6 windows vms( 2012r2 ) on one single server.
  auto rebooting scripts in windows guest.
  after one day (around hundred rebooting), can get 0x5c certainly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660519/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

4.8 kernels are not affected by this bug. If you have OOMs on 4.8
kernels, please file a new bug with all the revelant details and logs.

Thanks.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

This bug is not about memory use. It's about the Linux kernel triggering
the OOM killer when higher-order (order 2) allocations are requested and
progress cannot be made. This affected Linux 4.7 on mainline and was
fixed on Linux 4.7 stable and Linux 4.8. When some fixes were backported
to 4.4.0-59 (4.4.0-58 was not affected), this bugs was introduced to
Xenial kernels and is now fixed on 4.4.0-63. Any behavior on 4.8 kernels
must be investigated separately, because all fixes that were backported
to 4.4.0-63 are already present in 4.8.

Can you please open a new bug and attach all logs and details you can,
so we can investigate your problem and provide a fix? Please, do not use
this bug, because the fixes would be different anyway, and even thought
the symptom may look like, we consider them different bugs.

I appreciate you opening a new bug and providing this new report.

Thanks.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

Hi, Mr. Iain Buclaw.

Memory usage reports could be related to something else. This bug was
introduced at 4.4.0-59, you mention 4.4.0-58. We could certainly
investigate the issue you see, just not on this bug. Much more data is
necessary, but, please, don't attach new data to this bug. Your report
relates to a different kernel, which has a very different memory
management code. I could ask you to test 4.4.0-63, but it still is
possible that you find problems there, because they are unrelated to
this bug.

Thank you.
Cascardo.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+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 1664912] Re: linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

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

Title:
  linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-
  xenial 4.4.0-63.84~14.04.2

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Committed
Status in linux-lts-xenial source package in Zesty:
  Invalid

Bug description:
  Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-xenial/20170214_051856_a19a2@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664912/+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 1667066] Re: linux: 4.8.0-40.43 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux: 4.8.0-40.43 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-stable-phase-changed:Wednesday, 22. February 2017 21:31 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667066/+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 1667052] Re: linux: 4.4.0-65.86 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux: 4.4.0-65.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Thursday, 23. February 2017 15:46 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667052/+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 1651981] Re: shaking screen

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

Title:
  shaking screen

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

Bug description:
  After login into Ubuntu the screen starts to shake permanently.
  The login screen is still fine, problem start after log in.
  The problem is caused by last kernel update: running Ubuntu with the older 
kernel 4.8.0-30-generic fixes the issue.

  Upstream patch submission:
  https://lists.freedesktop.org/archives/dri-devel/2016-December/128331.html

  WORKAROUND: Revert:
  # first bad commit: [9cc4fd5b9fbb0d74e77c81521da1e2fe712f6787] 
drm/radeon/si_dpm: workaround for SI kickers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   7797 F pulseaudio
   /dev/snd/controlC1:  afiergol   7797 F pulseaudio
   /dev/snd/seq:timidity   6155 F timidity
  Date: Thu Dec 22 10:02:30 2016
  HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831
  InstallationDate: Installed on 2015-04-02 (629 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ZBook 15 G2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (66 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651981/+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 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 

[Kernel-packages] [Bug 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  apparmor's raw_data file in securityfs is sometimes truncated

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

Bug description:
  Hi,

  It looks like sometimes apparmor's securityfs output is sometimes
  truncated,

  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al
  total 0
  drwxr-xr-x  3 root root 0 Nov  3 16:45 .
  drwxr-xr-x 13 root root 0 Nov  3 16:44 ..
  -r--r--r--  1 root root 0 Nov  3 16:45 attach
  -r--r--r--  1 root root 0 Nov  3 16:45 mode
  -r--r--r--  1 root root 0 Nov  3 16:45 name
  drwxr-xr-x  3 root root 0 Nov  3 16:45 profiles
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_abi
  -r--r--r--  1 root root 46234 Nov  3 16:45 raw_data
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_hash
  -r--r--r--  1 root root 0 Nov  3 16:45 sha1
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 cat raw_data > /tmp/out
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al /tmp/out 
  -rw-r--r-- 1 root root 4009 Nov  3 16:55 /tmp/out

  and

  2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/
  2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size 
of the policy
  2016-11-03 10:59:20 @jjohansen  tych0: hrmm interesting, can you zip up the 
/tmp/out file so I can see it looks like a complete policy file?
  2016-11-03 11:00:03 @jjohansen  something is definitely not right there. hrmmm
  2016-11-03 11:00:26 @jjohansen  the size is set by the input buffer size
  2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out
  2016-11-03 11:00:36 tych0 yeah, i assume
  2016-11-03 11:01:15 @jjohansen  my guess is something is messing up in the 
seq_file walk of the policy
  2016-11-03 11:02:38 @jjohansen  tych0: yep the file is truncated, can you 
open a bug and I will start looking for it
  2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux?
  2016-11-03 11:03:35 @jjohansen  tych0: yeah for now, just linux
  2016-11-03 11:03:43 @jjohansen  we can add others if needed later
  2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue 
sometimes it works and sometimes it doesn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638996/+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 1661030] Re: regession tests failing after stackprofile test is run

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  regession tests failing after stackprofile test is run

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

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running setattr

  running symlink

  running syscall

  

[Kernel-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in tor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in tor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Committed
Status in tor source package in Yakkety:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+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 1656121] Re: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  unexpected errno=13 and disconnected path when trying to open
  /proc/1/ns/mnt from a unshared mount namespace

Status in AppArmor:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  This bug is based on a discussion with jjohansen on IRC.

  While working on a feature for snapd
  (https://github.com/snapcore/snapd/pull/2624) we came across an
  unexpected EACCES that only seems to happen when apparmor is in the
  loop.

  The kernel log shows something interesting. The full log is available
  here: http://paste.ubuntu.com/23789099/

  Jan 12 23:16:43 autopkgtest kernel: [  498.616822] audit: type=1400
  audit(1484259403.009:67): apparmor="ALLOWED" operation="open"
  info="Failed name lookup - disconnected path" error=-13 profile="snap
  .test-snapd-tools.cmd//null-/usr/bin/snap//null-/usr/lib/snapd/snap-
  confine" name="" pid=25299 comm="snap-confine" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  The code that triggers this is reproduced below (also visible here
  https://github.com/snapcore/snapd/pull/2624/files)

  +void sc_reassociate_with_pid1_mount_ns()
   +{
   +int init_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +int self_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +
   +debug("checking if the current process shares mount namespace"
   +  "with the init process");
   +
   +init_mnt_fd = open("/proc/1/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (init_mnt_fd < 0) {
   +die("cannot open mount namespace of the init process (O_PATH)");
   +}
   +self_mnt_fd = open("/proc/self/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (self_mnt_fd < 0) {
   +die("cannot open mount namespace of the current process 
(O_PATH)");
   +}
   +char init_buf[128], self_buf[128];
   +memset(init_buf, 0, sizeof init_buf);
   +if (readlinkat(init_mnt_fd, "", init_buf, sizeof init_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the init process");
   +}
   +memset(self_buf, 0, sizeof self_buf);
   +if (readlinkat(self_mnt_fd, "", self_buf, sizeof self_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the current process");
   +}
   +if (memcmp(init_buf, self_buf, sizeof init_buf) != 0) {
   +debug("the current process does not share mount namespace with "
   +  "the init process, re-association required");
   +// NOTE: we cannot use O_NOFOLLOW here because that file will 
always be a
   +// symbolic link. We actually want to open it this way.
   +int init_mnt_fd_real
   +__attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC);
   +if (init_mnt_fd_real < 0) {
   +die("cannot open mount namespace of the init process");
   +}
   +if (setns(init_mnt_fd_real, CLONE_NEWNS) < 0) {
   +die("cannot re-associate the mount namespace with the 
init process");
   +}
   +} else {
   +debug("re-associating is not required");
   +}
   +}

  The specific part that causes the error is:

   +  init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY |
  O_CLOEXEC);

  The call to open returns -1 and errno set to 13 (EACCES) despite using
  attach_disconnected.

  The code in question is executed from a seguid root executable that
  runs under a complain-mode profile (it is started from a process that
  is already confined with such a profile). All of the profiles are
  using attach_disconnected.

  I can reproduce this issue each time by running:

  spread -debug -v qemu:ubuntu-16.04-64:tests/regression/lp-1644439

  Against the code in this pull request:

  https://github.com/snapcore/snapd/pull/2624

  Which is git://github.com/zyga/snapd in the "reassociate-fix" branch

  Appropriate qemu images can be made using instructions from:

  https://github.com/zyga/spread-qemu-images

  I'm also happy to try any test kernels as I can easily run those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1656121/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1667052] Re: linux: 4.4.0-65.86 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-65.86 -proposed tracker

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

Title:
  linux: 4.4.0-65.86 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Thursday, 23. February 2017 15:46 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667052/+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 1557690] Re: s390/kconfig: CONFIG_NUMA without CONFIG_NUMA_EMU does not make any sense on s390x

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  s390/kconfig: CONFIG_NUMA without CONFIG_NUMA_EMU does not make any
  sense on s390x

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

Bug description:
  == Comment: #0 - Hendrik Brueckner - 2016-03-15 06:33:03 ==
  For NUMA, ensure the setting of these kernel configuration for s390x:

  # CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
  CONFIG_NUMA_EMU=y
  CONFIG_EMU_SIZE=0x1000

  
  CONFIG_NUMA without CONFIG_NUMA_EMU does not make any sense. s390 does not 
provide hardware topology information. However, we do support fake NUMA to 
improve performance issues seen with very large memory configurations. 
Therefore, CONFIG_NUMA_EMU has to be enabled.

  Given that we only support fake NUMA
  CONFIG_NUMA_BALANCING_DEFAULT_ENABLED should be disabled, since it
  moves pages without any benefit but costs additional cpu cycles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690/+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 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+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 1662673] Re: systemd-udevd hung in blk_mq_freeze_queue_wait testing unpartitioned NVMe drive

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  systemd-udevd hung in blk_mq_freeze_queue_wait testing unpartitioned
  NVMe drive

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

Bug description:
  For reference, here is the stack of systemd-udevd seen in the hang:

  [ 1558.214013] INFO: task systemd-udevd:1778 blocked for more than 120 
seconds.
  [ 1558.214318] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1558.214556] systemd-udevd   D 3fff8dbdf7a0 0  1778  1 
0x0004
  [ 1558.214637] Call Trace:
  [ 1558.214673] [c4ad3790] [c07aac20] 
schedule_timeout+0x180/0x2f0 (unreliable)
  [ 1558.214779] [c4ad3960] [c00158d0] __switch_to+0x200/0x350
  [ 1558.214870] [c4ad39c0] [c07adbb4] __schedule+0x414/0x9e0
  [ 1558.214961] [c4ad3a90] [c03b4e54] 
blk_mq_freeze_queue_wait+0x64/0xd0
  [ 1558.215107] [c4ad3af0] [d00034011964] 
nvme_revalidate_disk+0xd4/0x3a0 [nvme]
  [ 1558.215386] [c4ad3b90] [c03c2398] 
rescan_partitions+0x98/0x390
  [ 1558.215508] [c4ad3c60] [c03bb7ac] 
__blkdev_reread_part+0x9c/0xd0
  [ 1558.215599] [c4ad3c90] [c03bb818] 
blkdev_reread_part+0x38/0x70
  [ 1558.215935] [c4ad3cc0] [c03bc334] blkdev_ioctl+0x3b4/0xb80
  [ 1558.216016] [c4ad3d20] [c02cbcd0] block_ioctl+0x70/0x90
  [ 1558.216114] [c4ad3d40] [c0296b38] do_vfs_ioctl+0x458/0x740
  [ 1558.216192] [c4ad3dd0] [c0296ee4] SyS_ioctl+0xc4/0xe0
  [ 1558.216275] [c4ad3e30] [c000a17c] system_call+0x38/0xb4

  It appears that systemd-udevd is triggering every time HTX writes to
  the boot sector (partition table) of the raw drive, and this is
  causing the revalidate calls which expose the issue with the block
  driver mq freeze. With a partition table on each drive, HTX will no
  longer be writing the partition table and no longer triggering systemd
  to re-read the partition table and try to freeze I/O.

  The fix for this is provided by the following upstream commit:

  966d2b0 percpu-refcount: fix reference leak during percpu-atomic
  transition

  which needs to be pulled into 16.04 (as well as newer releases).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662673/+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 1660833] Re: apparmor reference count bug in label_merge_insert()

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor reference count bug in label_merge_insert()

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

Bug description:
  @new does not have a reference taken locally and should not have its  
  
  reference put locally either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1660994] Re: Xenial update to v4.4.46 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to v4.4.46 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.46 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.46 stable release shall be
  applied:

  fbdev: color map copying bounds checking
  tile/ptrace: Preserve previous registers for short regset write
  drm: Fix broken VT switch with video=1366x768 option
  mm/mempolicy.c: do not put mempolicy before using its nodemask
  sysctl: fix proc_doulongvec_ms_jiffies_minmax()
  ISDN: eicon: silence misleading array-bounds warning
  RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
  s390/ptrace: Preserve previous registers for short regset write
  can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
  can: ti_hecc: add missing prepare and unprepare of the clock
  ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
  ARC: [arcompact] handle unaligned access delay slot corner case
  parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
  nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
  NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
  SUNRPC: cleanup ida information when removing sunrpc module
  drm/i915: Don't leak edid in intel_crt_detect_ddc()
  IB/ipoib: move back IB LL address into the hard header
  IB/umem: Release pid in error and ODP flow
  s5k4ecgx: select CRC32 helper
  pinctrl: broxton: Use correct PADCFGLOCK offset
  platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
  mm, memcg: do not retry precharge charges
  Linux 4.4.46

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660994/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor not checking error if security_pin_fs() fails

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

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1660846] Re: apparmor leaking securityfs pin count

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor leaking securityfs pin count

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

Bug description:
  apparmor is leaking pinfs refcoutn when inode setup fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660846/+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 1662554] Re: [Yakkety SRU] Enable KEXEC support in ARM64 kernel

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  [Yakkety SRU] Enable KEXEC support in ARM64 kernel

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

Bug description:
  [Impact]
   * If the kernel is not built with CONFIG_KEXEC support, kexec-tools will not 
be able to live boot a new kernel over the running one.
   * Our partners/customers have requested this feature.

  [Test Case]
   * Install a version of kexec-tools that supports ARM64
   * Run the command: sudo kexec -l /boot/ --initrd=/boot/ 
--append="
   * You should see the message:  kexec_load failed: Function not implemented

  [Regression Potential]
   * The proposed config changes are limited to ARM64 architecture, overall 
risk of regression is low.

  [Other Info]
   * Please note that kexec-tools currently is not built for ARM64
   * I have an SRU to enable that https://bugs.launchpad.net/bugs/1659618
   * I am working with dannf to get kexec-tools to support ARM64 in yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662554/+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 1660849] Re: apparmor refcount leak of profile namespace when removing profiles

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor refcount leak of profile namespace when removing profiles

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

Bug description:
  When doing profile removal, the parent ns of the profiles is taken,
  but the reference isn't being put, resulting in the ns never being
  freed even after it is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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 1660993] Re: Xenial update to v4.4.45 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to v4.4.45 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.45 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.45 stable release shall be
  applied:

  ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
  IB/mlx5: Wait for all async command completions to complete
  IB/mlx4: Set traffic class in AH
  IB/mlx4: Fix out-of-range array index in destroy qp flow
  IB/mlx4: Fix port query for 56Gb Ethernet links
  IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
  IB/IPoIB: Remove can't use GFP_NOIO warning
  perf scripting: Avoid leaking the scripting_context variable
  ARM: dts: imx31: fix clock control module interrupts description
  ARM: dts: imx31: move CCM device node to AIPS2 bus devices
  ARM: dts: imx31: fix AVIC base address
  tmpfs: clear S_ISGID when setting posix ACLs
  x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
  svcrpc: don't leak contexts on PROC_DESTROY
  fuse: clear FR_PENDING flag when moving requests out of pending queue
  PCI: Enumerate switches below PCI-to-PCIe bridges
  HID: corsair: fix DMA buffers on stack
  HID: corsair: fix control-transfer error handling
  mmc: mxs-mmc: Fix additional cycles after transmission stop
  ieee802154: atusb: do not use the stack for buffers to make them DMA able
  mtd: nand: xway: disable module support
  x86/ioapic: Restore IO-APIC irq_chip retrigger callback
  qla2xxx: Fix crash due to null pointer access
  ubifs: Fix journal replay wrt. xattr nodes
  clocksource/exynos_mct: Clear interrupt when cpu is shut down
  svcrdma: avoid duplicate dma unmapping during error recovery
  ARM: 8634/1: hw_breakpoint: blacklist Scorpion CPUs
  ceph: fix bad endianness handling in parse_reply_info_extra
  ARM: dts: da850-evm: fix read access to SPI flash
  arm64/ptrace: Preserve previous registers for short regset write
  arm64/ptrace: Preserve previous registers for short regset write - 2
  arm64/ptrace: Preserve previous registers for short regset write - 3
  arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
  arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
  ARM: dts: imx6qdl-nitrogen6_max: fix sgtl5000 pinctrl init
  ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation
  ARM: 8613/1: Fix the uaccess crash on PB11MPCore
  blackfin: check devm_pinctrl_get() for errors
  ite-cir: initialize use_demodulator before using it
  dmaengine: pl330: Fix runtime PM support for terminated transfers
  selftest/powerpc: Wrong PMC initialized in pmc56_overflow test
  arm64: avoid returning from bad_mode
  Linux 4.4.45

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660993/+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 1661430] Re: [Hyper-V] Fix ring buffer handling to avoid host throttling

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  [Hyper-V] Fix ring buffer handling to avoid host throttling

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

Bug description:
  An unfortunate side effect of some of the recent work done to improve
  ring buffer performance made a situation where the host would
  interpret guest requests as a denial of service attack, pausing guest
  communications for five seconds. This series of fixes corrects this
  problem.

  Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv:
  vmbus: Fix signaling logic in hv_need_to_signal_on_read()")

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e

  Drivers: hv: vmbus: Base host signaling strictly on the ring state
  One of the factors that can result in the host concluding that a given
  guest in mounting a DOS attack is if the guest generates interrupts
  to the host when the host is not expecting it. If these "spurious"
  interrupts reach a certain rate, the host can throttle the guest to
  minimize the impact. The host computation of the "expected number
  of interrupts" is strictly based on the ring transitions. Until
  the host logic is fixed, base the guest logic to interrupt solely
  on the ring state.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884

  Drivers: hv: vmbus: On write cleanup the logic to interrupt the host
  Signal the host when we determine the host is to be signaled.
  The currrent code determines the need to signal in the ringbuffer
  code and actually issues the signal elsewhere. This can result
  in the host viewing this interrupt as spurious since the host may also
  poll the channel. Make the necessary adjustments.

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=3372592a140db69fd63837e81f048ab4abf8111e

  Drivers: hv: vmbus: On the read path cleanup the logic to interrupt the host
  Signal the host when we determine the host is to be signaled -
  on th read path. The currrent code determines the need to signal in the
  ringbuffer code and actually issues the signal elsewhere. This can result
  in the host viewing this interrupt as spurious since the host may also
  poll the channel. Make the necessary adjustments.

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=433e19cf33d34bb6751c874a9c00980552fe508c

  Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
  Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
  hv_need_to_signal_on_read()")
  added the proper mb(), but removed the test "prev_write_sz < pending_sz"
  when making the signal decision.

  As a result, the guest can signal the host unnecessarily,
  and then the host can throttle the guest because the host
  thinks the guest is buggy or malicious; finally the user
  running stress test can perceive intermittent freeze of
  the guest.

  This patch brings back the test, and properly handles the
  in-place consumption APIs used by NetVSC (see get_next_pkt_raw(),
  put_pkt_raw() and commit_rd_index()).

  Fixes: a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
  hv_need_to_signal_on_read()")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661430/+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 1660845] Re: apparmor reference count leak when securityfs_setup_d_inode\ () fails

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor reference count leak when securityfs_setup_d_inode\ () fails

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

Bug description:
  apparmor is leaking the parent ns ref count, by directly returning the
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660845/+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 1662096] Re: ipv6: fix a refcnt leak with peer addr

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  ipv6: fix a refcnt leak with peer addr

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The following upstream patch is missing in ubuntu-14.04:
  f24062b07dda ipv6: fix a refcnt leak with peer addr

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662096/+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 1662507] Re: Xenial update to v4.4.47 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to v4.4.47 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.47 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.47 stable release shall be
  applied:

  r8152: fix the sw rx checksum is unavailable
  mlxsw: spectrum: Fix memory leak at skb reallocation
  mlxsw: switchx2: Fix memory leak at skb reallocation
  mlxsw: pci: Fix EQE structure definition
  net: lwtunnel: Handle lwtunnel_fill_encap failure
  net: ipv4: fix table id in getroute response
  net: systemport: Decouple flow control from __bcm_sysport_tx_reclaim
  tcp: fix tcp_fastopen unaligned access complaints on sparc
  openvswitch: maintain correct checksum state in conntrack actions
  ravb: do not use zero-length alignment DMA descriptor
  ax25: Fix segfault after sock connection timeout
  net: fix harmonize_features() vs NETIF_F_HIGHDMA
  net: phy: bcm63xx: Utilize correct config_intr function
  ipv6: addrconf: Avoid addrconf_disable_change() using RCU read-side lock
  tcp: initialize max window for a new fastopen socket
  bridge: netlink: call br_changelink() during br_dev_newlink()
  r8152: don't execute runtime suspend if the tx is not empty
  af_unix: move unix_mknod() out of bindlock
  qmi_wwan/cdc_ether: add device ID for HP lt2523 (Novatel E371) WWAN card
  net: dsa: Bring back device detaching in dsa_slave_suspend()
  Linux 4.4.47

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662507/+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 1663657] Re: Xenial update to v4.4.48 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to v4.4.48 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.48 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.48 stable release shall be
  applied:

  PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies
  ext4: validate s_first_meta_bg at mount time
  drm/nouveau/disp/gt215: Fix HDA ELD handling (thus, HDMI audio) on gt215
  drm/nouveau/nv1a,nv1f/disp: fix memory clock rate retrieval
  crypto: api - Clear CRYPTO_ALG_DEAD bit before registering an alg
  crypto: arm64/aes-blk - honour iv_out requirement in CBC and CTR modes
  perf/core: Fix PERF_RECORD_MMAP2 prot/flags for anonymous memory
  ata: sata_mv:- Handle return value of devm_ioremap.
  libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices
  powerpc/eeh: Fix wrong flag passed to eeh_unfreeze_pe()
  powerpc: Add missing error check to prom_find_boot_cpu()
  NFSD: Fix a null reference case in find_or_create_lock_stateid()
  svcrpc: fix oops in absence of krb5 module
  zswap: disable changing params if init fails
  cifs: initialize file_info_lock
  mm/memory_hotplug.c: check start_pfn in test_pages_in_a_zone()
  mm, fs: check for fatal signals in do_generic_file_read()
  can: bcm: fix hrtimer/tasklet termination in bcm op removal
  mmc: sdhci: Ignore unexpected CARD_INT interrupts
  percpu-refcount: fix reference leak during percpu-atomic transition
  HID: wacom: Fix poor prox handling in 'wacom_pl_irq'
  KVM: x86: do not save guest-unsupported XSAVE state
  USB: serial: qcserial: add Dell DW5570 QDL
  USB: serial: pl2303: add ATEN device ID
  USB: Add quirk for WORLDE easykey.25 MIDI keyboard
  usb: gadget: f_fs: Assorted buffer overflow checks.
  USB: serial: option: add device ID for HP lt2523 (Novatel E371)
  x86/irq: Make irq activate operations symmetric
  base/memory, hotplug: fix a kernel oops in show_valid_zones()
  Linux 4.4.48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663657/+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 1660834] Re: apparmor label leak when new label is unused

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor label leak when new label is unused

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

Bug description:
  When a new label is created, it is created with a proxy in a circular 
  
  ref count that is broken by replacement. However if the label is not  
  
  used it will never be replaced and the circular ref count will never  
  
  be broken resulting in a leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor  auditing denied access of special apparmor .null fi\ le

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

Bug description:
  When an fd is disallowed from being inherited during exec, instead of 
  
  closed it is duped to a special apparmor/.null file. This prevents the
  
  fd from being reused by another file in case the application expects  
  
  the original file on a give fd (eg stdin/stdout etc). This results in 
  
  a denial message like 
  
  [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" 
op\
  eration="file_inherit" namespace="root//lxd-t_" 
profile="/sbin/dhc\
  lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" 
denied_m\
  ask="wr" fsuid=165536 ouid=165536 
  

  
  Further access to the fd is resultin in the rather useless denial message 
  
  of
  
  [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" 
op\
  eration="file_perm" namespace="root//lxd-t_" 
profile="/sbin/dhclie\
  nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" 
denied_\
  mask="w" fsuid=165536 ouid=0  
  

  
  since we have the original denial, the noisy and useless .null based  
  
  denials can be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1659417] Re: docker permission issues with overlay2 storage driver

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  docker permission issues with overlay2 storage driver

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

Bug description:
  SRU Justification

  Impact: Under some conditions docker users using the overlay2 storage
  driver with xenial kernels will get "permission denied" errors when
  they should not. This is due to a bug in overlayfs.

  Fix: Backport upstream fix, plus some cleanup to make the backup
  cleaner.

  Regression Potential: All changes are straightforward and have low
  risk of introducing regressions.

  ---

  Due to an issue in overlayfs, in some scenrios docker users can get
  erroneous "permission denied" errors when using the overlay2 storage
  driver. When a user has search permissions on the upper dir but not
  the lower dir they may get this error, where having search permissions
  for the upper dir should be sufficient. This is fixed by upstream
  commit 38b78a5f18584db6fa7441e0f4531b283b0e6725.

  Originally reported at https://github.com/docker/docker/issues/28391.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659417/+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 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  apparmor oops in bind_mnt when dev_path lookup fails

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

Bug description:
  Bind mounts can oops when devname lookup fails because the devname is 
  
  unintialized and used in auditing the denial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1593293] Re: brd module compiled as built-in

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  brd module compiled as built-in

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

Bug description:
  Block RAM disk module (brd, CONFIG_BLK_DEV_RAM) compiled as 'y', that
  means it is 'built-in' and can not be unloaded or loaded with
  different parameters. This render module completely useless because
  user can not anymore change it size.

  Please change it back to 'm' (module) to allow users use this module.

  Affected kernels (so far): Xenial, Yakkety (4.4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593293/+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 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Committed
Status in apparmor source package in Zesty:
  New
Status in linux source package in Zesty:
  In Progress

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1624164] Re: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for
  module i915_bpo

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Won't Fix

Bug description:
  SRU Justification

  Impact: i915_bpo requests some optional firmware which is not present
  in xenial due to causing regressions on some hardware. This produces a
  warning when generating the initrds.

  Fix: Remove the MODULE_FIRMWARE statement for this driver, thus
  removing it from the firmware's modinfo and eliminating the warning.

  Regression Potential: Virtually no risk of regression since it only
  affects the modinfo section of the kernel module and not the runtime
  behavior.

  ---

  Also: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin
  for module i915_bpo

  Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for
  module i915_bpo

  Ubuntu 16.04 Xenial

  Packages:

  ii  linux-firmware1.157.3   all   Firmware 
for Linux kernel drivers
  ii  linux-image-generic   4.4.0.36.38   amd64 Generic 
Linux kernel image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624164/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

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

Title:
  Linux kernel 4.8 hangs at boot up

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

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1655420] Re: Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang with a zero window

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session
  to hang with a zero window

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

Bug description:
  == Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

  This bug is being mirrored for any distributions that include ibmveth
  large send/receive support.  In short, any distribution with ibmveth
  v1.05 will be affected (releases 14.04.5/Wily+)

  2 upstream commits:

  1. Set GSO size and type
  
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
  2. set GSO segments
  
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

  A VIOS fix is needed as well.

  ---Problem Description---
  When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655420/+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 1656913] Re: NVMe: adapter is missing after abnormal shutdown followed by quick reboot, quirk needed

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1656913

Title:
  NVMe: adapter is missing after abnormal shutdown followed by quick
  reboot, quirk needed

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

Bug description:
  Canonical, we would like to request the merge of the following patch
  to Xenial (4.4.0-x) and Yakkety (4.8.0-y) kernels if possible.

  b5a10c5f75 ("nvme: apply DELAY_BEFORE_CHK_RDY quirk at probe time too")
  
[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b5a10c5]

  This is a very non-intrusive patch, just extending a quirk already
  present - without this patch, after an abnormal shutdown of the
  machine (followed by a quick reboot), the NVMe device from HGST
  becomes unresponsive and we need to force a PCI rescan as workaround,
  a procedure that does not always work.

  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656913/+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 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1625318

Title:
  Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running
  ping will stop working

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

Bug description:
  ---Problem Description---
  If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing 
something like a ping flood. The PF interface will stop pinging. 
  We found a small window were MMIO are bein g disabled during pci_enable_sriov 
is called. 
   
  ---uname output---
  4.4.0-30-generic
   
  ---Additional Hardware Info---
  It needs a Mellanox CX4 SRIOV capable to recreate this issue 

  Machine Type = P8 

  ---Steps to Reproduce---
   just configure the IP address of PF interface and start like a ping flood to 
that interface.
  then do this echo to enable SRIOV on the PF. 
  echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs
  Then you will notice the ping flood will stop. 
   
  A patch that will fix this issue was sent for review:
  https://patchwork.ozlabs.org/patch/671517/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+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 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running
  ping will stop working

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

Bug description:
  ---Problem Description---
  If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing 
something like a ping flood. The PF interface will stop pinging. 
  We found a small window were MMIO are bein g disabled during pci_enable_sriov 
is called. 
   
  ---uname output---
  4.4.0-30-generic
   
  ---Additional Hardware Info---
  It needs a Mellanox CX4 SRIOV capable to recreate this issue 

  Machine Type = P8 

  ---Steps to Reproduce---
   just configure the IP address of PF interface and start like a ping flood to 
that interface.
  then do this echo to enable SRIOV on the PF. 
  echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs
  Then you will notice the ping flood will stop. 
   
  A patch that will fix this issue was sent for review:
  https://patchwork.ozlabs.org/patch/671517/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+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 1655002] Re: Move some kernel modules to the main kernel package (part 2)

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1655002

Title:
  Move some kernel modules to the main kernel package (part 2)

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

Bug description:
  Hello Canonical,

  there are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  Our suggestion is to add these important modules to the main kernel
  package, so we do not require the installation of the -extra package.

  One round of additions was already completed. But we verified some
  modules we need were missing, so we are hereby requesting a 2nd round
  of module additions to linux-image main package of Xenial and Yakkety
  (and all future releases).

  The list is:


  (AST stack)
  1. ast
  2. i2c-core
  3. sysfillrect
  4. syscopyarea
  5. sysimgblt
  6. fb_sys_fops
  7. drm
  8. drm_kms_helper
  9. ttm
  10. i2c-algo-bit

  11. kvm
  12. kvm_pr
  13. kvm_hv
  14. vmx_crypto
  15. at24
  16. nvmem_core
  17. cmdlinepart
  18. input_leds
  19. uio
  20. uio_pdrv_genirq
  21. ofpart

  (USB stack)
  22. usb_storage
  23. uas
  24. hid
  25. hid_generic
  26. usbhid


  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU REQUEST [Xenial, Yakkety, Zesty] ==

  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

  == Fix ==

  Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses
  the issue.  The patch has been accepted into the upstream queue for
  4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html

  == Test Case ==

  run 10 times:
  sudo stress-ng --fstat 128 -t 60 -v

  Without the fix, it will hang, with the fix there is no hang or USB
  error messages.

  == Regression Potential ==

  This only quirks a specific AMI virtual keyboard and mouse into a poll
  mode, so it touches one device. Futhermore, the poll mode shouldn't
  affect operation; it just makes the URB handling less efficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1652132/+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 1654067] Re: Ubuntu 16.10 KVM: Running out of memory if trying to bringup guest with more than 64VFs.

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

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

Title:
  Ubuntu 16.10 KVM: Running out of memory if trying to bringup guest
  with more than 64VFs.

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

Bug description:
  == Comment: #0 - Carol L. Soto - 2017-01-04 12:03:57 ==
  ---Problem Description---
  If user try to create a guest with more than 64 VFs then the guest will have 
issues to come up but if user keeps trying to bringup this guest over and over 
the system will eventually start seeing out of memory messages. 
  Like this:
  Jan  3 14:33:13 ltc-fire1 kernel: [ 1053.950753] systemd invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950757] systemd cpuset=/ 
mems_allowed=0
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950761] CPU: 104 PID: 1 Comm: 
systemd Tainted: G   OE   4.8.0-34-generic #36-Ubuntu
  Jan  3 14:33:16 ltc-fire1 kernel: [ 1053.950763] Call Trace:

   
  ---uname output---
  Linux ltc-fire1 4.8.0-34-generic #36 SMP Tue Jan 3 15:27:22 CST 2017 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  we are using Mellanox CX4 card with SRIOV enabled to be able to create a 
guest with more than 64 VFs.  

   
  Machine Type = P8 
   

  ---Steps to Reproduce---
   create a guest with more than 64 VFs and then just try to bring up the guest 
by 
  virsh start --console ltc-fire1-vm3-ubuntu-16.10-69VFs.
  Will attach example guest xml.

  == Comment: #2 - Carol L. Soto - 2017-01-04 12:09:32 ==
  If I build a kernel with these upstream patches, then I do not see the memory 
leaks messages in dmesg:

  From 88f54a3581eb9deaa3bd1aade40aef266d782385 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:51:59 +1100
  Subject: powerpc/iommu: Pass mm_struct to init/cleanup helpers

  From d7baee6901b34c4895eb78efdbf13a49079d7404 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:00 +1100
  Subject: powerpc/iommu: Stop using @current in mm_iommu_xxx

  From 39701e56f5f16ea0cf8fc9e8472e645f8de91d23 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:01 +1100
  Subject: vfio/spapr: Postpone allocation of userspace version of TCE table

  From 6f01cc692a16405235d5c34056455b182682123c Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:02 +1100
  Subject: vfio/spapr: Add a helper to create default DMA window

  From d9c728949ddc9de5734bf3b12ea906ca8a77f2a0 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:03 +1100
  Subject: vfio/spapr: Postpone default window creation

  From bc82d122ae4a0e9f971f13403995898fcfa0c09e Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:04 +1100
  Subject: vfio/spapr: Reference mm in tce_container

  From 4b6fad7097f883335b6d9627c883cb7f276d94c9 Mon Sep 17 00:00:00 2001
  From: Alexey Kardashevskiy 
  Date: Wed, 30 Nov 2016 17:52:05 +1100
  Subject: powerpc/mm/iommu, vfio/spapr: Put pages on VFIO container shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654067/+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 1650059] Re: [Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the upstream 4.9 kernel

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1650059

Title:
  [Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the upstream 4.9
  kernel

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

Bug description:
  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  The following commits are upstream in the 4.9 kernel release:

  mshyperv.c : commit 186f43608a5c827f8284fe4559225b4dccaa49ef : 
x86/kernel: Audit and remove any unnecessary uses of module.h
  hyperv.h : commit 509879bdb30b8e12bd0b3cb0bc8429f01478df4b : Drivers: hv: 
Introduce a policy for controlling channel affinity
  hyperv.h : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : Drivers: hv: 
get rid of id in struct vmbus_channel
  hyperv.h : commit 0f98829a99850836cf7c2cc9fbf1d7ce0f795780 : Drivers: hv: 
vmbus: suppress some "hv_vmbus: Unknown GUID" warnings
  hyperv.h : commit 8e1d260738ca89bc7c87444f95f04a026d12b496 : Drivers: hv: 
utils: Support TimeSync version 4.0 protocol samples.
  hyperv.h : commit 638fea33aee858cc665297a76f0039e95a28ce0c : Drivers: hv: 
vmbus: fix the race when querying & updating the percpu list
  channel.c : commit 3724287c0ec472815ebe5ae3790f77965c6aa557 : Drivers: 
hv: vmbus: Implement a mechanism to tag the channel for low latency
  channel.c : commit 4d63763296ab7865a98bc29cc7d77145815ef89f : Drivers: 
hv: get rid of redundant messagecount in create_gpadl_header()
  channel.c : commit 638fea33aee858cc665297a76f0039e95a28ce0c : Drivers: 
hv: vmbus: fix the race when querying & updating the percpu list
  channel.c : commit ccef9bcc02ee63ac171ea9f0d51e04b3e55b3a12 : Drivers: 
hv: vmbus: Enable explicit signaling policy for NIC channels
  channel_mgmt.c : commit 638fea33aee858cc665297a76f0039e95a28ce0c : 
Drivers: hv: vmbus: fix the race when querying & updating the percpu list
  channel_mgmt.c : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : 
Drivers: hv: get rid of id in struct vmbus_channel
  connection.c : commit 8de0d7e951826d7592e0ba1da655b175c4aa0923 : Drivers: 
hv: vmbus: Reduce the delay between retries in vmbus_post_msg()
  hv_balloon.c : commit eece30b9f0046cee810a2c7caa2247f3f8dc85e2 : Drivers: 
hv: balloon: replace ha_region_mutex with spinlock
  hv_balloon.c : commit b605c2d913589c448d4a6887262bb8e99da12009 : Drivers: 
hv: balloon: Use available memory value in pressure report
  hv.c : commit a9f61ca793becabdefab03b77568d6c6f8c1bc79 : Drivers: hv: 
avoid vfree() on crash
  mshyperv.c : commit 186f43608a5c827f8284fe4559225b4dccaa49ef : 
x86/kernel: Audit and remove any unnecessary uses of module.h
  hyperv.h : commit 509879bdb30b8e12bd0b3cb0bc8429f01478df4b : Drivers: hv: 
Introduce a policy for controlling channel affinity
  hyperv.h : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : Drivers: hv: 
get rid of id in struct vmbus_channel
  hyperv.h : commit 0f98829a99850836cf7c2cc9fbf1d7ce0f795780 : Drivers: hv: 
vmbus: suppress some "hv_vmbus: Unknown GUID" warnings
  hyperv.h : commit 8e1d260738ca89bc7c87444f95f04a026d12b496 : Drivers: hv: 
utils: Support 

[Kernel-packages] [Bug 1650059] Re: [Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the upstream 4.9 kernel

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  [Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the upstream 4.9
  kernel

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

Bug description:
  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  The following commits are upstream in the 4.9 kernel release:

  mshyperv.c : commit 186f43608a5c827f8284fe4559225b4dccaa49ef : 
x86/kernel: Audit and remove any unnecessary uses of module.h
  hyperv.h : commit 509879bdb30b8e12bd0b3cb0bc8429f01478df4b : Drivers: hv: 
Introduce a policy for controlling channel affinity
  hyperv.h : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : Drivers: hv: 
get rid of id in struct vmbus_channel
  hyperv.h : commit 0f98829a99850836cf7c2cc9fbf1d7ce0f795780 : Drivers: hv: 
vmbus: suppress some "hv_vmbus: Unknown GUID" warnings
  hyperv.h : commit 8e1d260738ca89bc7c87444f95f04a026d12b496 : Drivers: hv: 
utils: Support TimeSync version 4.0 protocol samples.
  hyperv.h : commit 638fea33aee858cc665297a76f0039e95a28ce0c : Drivers: hv: 
vmbus: fix the race when querying & updating the percpu list
  channel.c : commit 3724287c0ec472815ebe5ae3790f77965c6aa557 : Drivers: 
hv: vmbus: Implement a mechanism to tag the channel for low latency
  channel.c : commit 4d63763296ab7865a98bc29cc7d77145815ef89f : Drivers: 
hv: get rid of redundant messagecount in create_gpadl_header()
  channel.c : commit 638fea33aee858cc665297a76f0039e95a28ce0c : Drivers: 
hv: vmbus: fix the race when querying & updating the percpu list
  channel.c : commit ccef9bcc02ee63ac171ea9f0d51e04b3e55b3a12 : Drivers: 
hv: vmbus: Enable explicit signaling policy for NIC channels
  channel_mgmt.c : commit 638fea33aee858cc665297a76f0039e95a28ce0c : 
Drivers: hv: vmbus: fix the race when querying & updating the percpu list
  channel_mgmt.c : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : 
Drivers: hv: get rid of id in struct vmbus_channel
  connection.c : commit 8de0d7e951826d7592e0ba1da655b175c4aa0923 : Drivers: 
hv: vmbus: Reduce the delay between retries in vmbus_post_msg()
  hv_balloon.c : commit eece30b9f0046cee810a2c7caa2247f3f8dc85e2 : Drivers: 
hv: balloon: replace ha_region_mutex with spinlock
  hv_balloon.c : commit b605c2d913589c448d4a6887262bb8e99da12009 : Drivers: 
hv: balloon: Use available memory value in pressure report
  hv.c : commit a9f61ca793becabdefab03b77568d6c6f8c1bc79 : Drivers: hv: 
avoid vfree() on crash
  mshyperv.c : commit 186f43608a5c827f8284fe4559225b4dccaa49ef : 
x86/kernel: Audit and remove any unnecessary uses of module.h
  hyperv.h : commit 509879bdb30b8e12bd0b3cb0bc8429f01478df4b : Drivers: hv: 
Introduce a policy for controlling channel affinity
  hyperv.h : commit e7fca5d860aeeb1e606448f5191cea8d925cc7a3 : Drivers: hv: 
get rid of id in struct vmbus_channel
  hyperv.h : commit 0f98829a99850836cf7c2cc9fbf1d7ce0f795780 : Drivers: hv: 
vmbus: suppress some "hv_vmbus: Unknown GUID" warnings
  hyperv.h : 

[Kernel-packages] [Bug 1656913] Re: NVMe: adapter is missing after abnormal shutdown followed by quick reboot, quirk needed

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  NVMe: adapter is missing after abnormal shutdown followed by quick
  reboot, quirk needed

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

Bug description:
  Canonical, we would like to request the merge of the following patch
  to Xenial (4.4.0-x) and Yakkety (4.8.0-y) kernels if possible.

  b5a10c5f75 ("nvme: apply DELAY_BEFORE_CHK_RDY quirk at probe time too")
  
[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b5a10c5]

  This is a very non-intrusive patch, just extending a quirk already
  present - without this patch, after an abnormal shutdown of the
  machine (followed by a quick reboot), the NVMe device from HGST
  becomes unresponsive and we need to force a PCI rescan as workaround,
  a procedure that does not always work.

  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656913/+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 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657540/+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 1656381] Re: Xen MSI setup code incorrectly re-uses cached pirq

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1656381

Title:
  Xen MSI setup code incorrectly re-uses cached pirq

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

Bug description:
  [Impact]

  This bug fixes the root problem reported in bug 1648449, so its
  description can be mostly reused here:

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system. If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with multiple NVMe drives. All except the first
  will fail to initialize, and errors will appear in the system log (if
  the system boots at all). With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the Xen MSI setup function may cause problems with other PCI
  devices using MSI/MSIX interrupts on a Xen guest.

  Note this patch restores correct behavior for guests running under Xen
  4.5 or later hypervisors - specifically Xen hypervisors with qemu
  2.1.0 or later.  For Xen hypervisors with qemu 2.0.0 or earlier, this
  patch causes a regression.  With an Ubuntu hypervisor, Vivid or later
  qemu is patched, as well as UCA Kilo or later qemu.  Trusty qemu or
  UCA Icehouse qemu are not patched - see bug 1657489.

  [Other Info]

  The patch from bug 1648449 was only a workaround, that changed the
  NVMe driver to not trigger this Xen bug.  However, there have been
  reports of that patch causing non-Xen systems with NVMe drives to stop
  working, in bug 1626894.  So, the best thing to do is revert the
  workaround patch (and its regression fix patch from bug 1651602) back
  to the original NVMe drive code, and apply the real Xen patch to fix
  the problem.  That should restore functionality for non-Xen systems,
  and should allow Xen systems with multiple NVMe controllers to work.

  Upstream discussion:
  https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html

  Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when
  driver unload")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656381/+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 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

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

Title:
  regression in linux-libc-dev in yakkety: C++ style comments are not
  allowed in ISO C90

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

Bug description:
  klibc is failing to build on arm64 in yakkety because of a change in
  unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
  4.8.0-36.38:

gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d  -nostdinc -iwithprefix 
include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64  
-I/<>/usr/include/bits64 -Iusr/include/bits64  
-I/<>/usr/klibc/../include -Iusr/klibc/../include  
-I/<>/usr/include -Iusr/include  -I/<>/linux/include 
-Ilinux/include  -I/<>/linux/arch/arm64/include 
-Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os 
-march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter  
 -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o 
usr/klibc/
  syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def
  In file included from /<>/linux/include/asm/unistd.h:19:0,
   from usr/klibc/SYSCALLS.def:13:
  /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style 
comments are not allowed in ISO C90
   //__SYSCALL(__NR_pkey_get,  sys_pkey_get)
   ^
  /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will 
be reported only once per input file)

  https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893

  We should reasonably expect the headers in linux-libc-dev to
  maximally-conformant C headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+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 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1658270

Title:
  Backport Dirty COW patch to prevent wineserver freeze

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: 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/1655842

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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 Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  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:bd12/09/2016: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/1655842/+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 1655379] Re: Bug fixes for IBM VNIC Driver

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

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

Title:
  Bug fixes for IBM VNIC Driver

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

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1650263] Re: [16.04.2] POWER9 patches on top of 4.8

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

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

Title:
  [16.04.2] POWER9 patches on top of 4.8

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

Bug description:
  This is a Ubuntu 16.04.2 feature to track the inclusions of POWER9
  patches on top of kernel 4.8.

  Ubuntu 16.04.2 is based on kernel 4.8[1], and we want to add support
  for POWER9 on this kernel. In order to do so, we will need to cherry-
  pick important patches.

  What are the commit ids for these patches?

  Once we have the first batch of commit-ids, we will get this feature
  mirrored to Canonical.

  [1] git://kernel.ubuntu.com/ubuntu/ubuntu-yakkety.git

  Canonical, this is a place holder at this moment. We will start to put
  the commits that would be required soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650263/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1652132

Title:
  Call trace when testing fstat stressor on ppc64el with virtual
  keyboard and mouse present

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU REQUEST [Xenial, Yakkety, Zesty] ==

  Ubuntu 16.04.1
  Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le

  When running the stress-ng "fstat" stressor, it is trying to access
  the USB bus and giving a call trace and locking up any further USB
  activity (lsusb hangs). This only seems to occur so far on
  openpower(Firestone and Garrison) where there is a virtual USB
  keyboard and mouse built into the BMC.

  From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American
  Megatrends, Inc. Virtual Keyboard and Mouse

  Another openpower server(Briggs) has no virtual usb devices and does
  not experience the failure.

  Please see attached kern.log and dmesg output for further details.

  == Fix ==

  Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses
  the issue.  The patch has been accepted into the upstream queue for
  4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html

  == Test Case ==

  run 10 times:
  sudo stress-ng --fstat 128 -t 60 -v

  Without the fix, it will hang, with the fix there is no hang or USB
  error messages.

  == Regression Potential ==

  This only quirks a specific AMI virtual keyboard and mouse into a poll
  mode, so it touches one device. Futhermore, the poll mode shouldn't
  affect operation; it just makes the URB handling less efficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1652132/+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 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1657540

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657540/+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 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1655683

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

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

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an _buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an _buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat 

[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety

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

Title:
  Backport Dirty COW patch to prevent wineserver freeze

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+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 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1630924

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+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 1657674] Re: Add support for RT5660 codec based sound cards on Baytrail

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: 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/1657674

Title:
  Add support for RT5660 codec based sound cards on Baytrail

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Support RT5660 (ALC3277) codec based sound cards on Ubuntu Xenial
  kernel

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1657674/+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 1655002] Re: Move some kernel modules to the main kernel package (part 2)

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  Move some kernel modules to the main kernel package (part 2)

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

Bug description:
  Hello Canonical,

  there are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  Our suggestion is to add these important modules to the main kernel
  package, so we do not require the installation of the -extra package.

  One round of additions was already completed. But we verified some
  modules we need were missing, so we are hereby requesting a 2nd round
  of module additions to linux-image main package of Xenial and Yakkety
  (and all future releases).

  The list is:


  (AST stack)
  1. ast
  2. i2c-core
  3. sysfillrect
  4. syscopyarea
  5. sysimgblt
  6. fb_sys_fops
  7. drm
  8. drm_kms_helper
  9. ttm
  10. i2c-algo-bit

  11. kvm
  12. kvm_pr
  13. kvm_hv
  14. vmx_crypto
  15. at24
  16. nvmem_core
  17. cmdlinepart
  18. input_leds
  19. uio
  20. uio_pdrv_genirq
  21. ofpart

  (USB stack)
  22. usb_storage
  23. uas
  24. hid
  25. hid_generic
  26. usbhid


  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1649718] Re: Linux rtc self test fails in a VM under xenial

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: 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/1649718

Title:
  Linux rtc self test fails in a VM under xenial

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

Bug description:
  == SRU Justification ==

  Impact: A race in kvm can result in the EOI signal for the rtc irq to
  be lost. After this happens no more rtc interrupts will be delivered
  to the guest.

  Fix: Three upstream cherry picks which fix the problem.

  Regression Potential: These patches have been upstream since 4.6, so
  they're well-tested at this point. Thus regressions are unlikely.

  ---

  ADT testing for the linux package hangs at the kernel's rtc selftest,
  for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/l/linux/20161212_132117_a258d@/log.gz

  Running this test manually, I've observed that this will hang in me
  with various kernel versions going back to 4.4 in a VM on my machine
  which is running xenial. The test runs to completion in a VM on a
  different machine running zesty.

  This is the section of the test which produces the hang:

  /* Turn on update interrupts (one per second) */
  retval = ioctl(fd, RTC_UIE_ON, 0);
  if (retval == -1) {
  if (errno == EINVAL) {
  fprintf(stderr,
  "\n...Update IRQs not supported.\n");
  goto test_READ;
  }
  perror("RTC_UIE_ON ioctl");
  exit(errno);
  }

  fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading 
%s:",
  rtc);
  fflush(stderr);
  for (i=1; i<6; i++) {
  /* This read will block */
  retval = read(fd, , sizeof(unsigned long));
  if (retval == -1) {
  perror("read");
  exit(errno);
  }
  fprintf(stderr, " %d",i);
  fflush(stderr);
  irqcount++;
  }

  The read blocks indefinitely most of the time. After boot it might
  return once or twice before it hangs, but running the test
  subsequently always hangs on the first read. I'll attach the full
  source for the test (rtctest.c).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649718/+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 1657682] Re: Support latest Redpine WLAN/BT RS9113 driver

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: 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/1657682

Title:
  Support latest Redpine WLAN/BT RS9113 driver

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.

  This is the latest version of the driver provided by Redpine. For now,
  this driver is enabled only on x86, x86_64 architectures.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1657682/+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 1640786] Re: netfilter regression introducing a performance slowdown in binary arp/ip/ip6tables

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  netfilter regression introducing a performance slowdown in binary
  arp/ip/ip6tables

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

Bug description:
  [SRU JUSTIFICATION]

  [Impact]

  It has been brought to my attention that Ubuntu kernel 4.4 has a
  severe netfilter regression affecting the performance of
  "/sbin/iptables" command, especially when adding large number of
  policies. My source have documented everything here[2].

  Note that the situation can also be reproduce with latest and greatest
  upstream kernel v4.9-rc4.

  I was able to reproduce the situation on my side, and a kernel bisect
  identified the same offending commit[1] as my source found for this
  bug.

  Running the commit right before the offending one have proven to have
  expected performance :

  # commit [71ae0dff] <== Offending commit
  real 0m33.314s
  user 0m1.520s
  sys 0m26.192s

  # commit [d7b59742] <== Right before offending commit
  real 0m5.952s
  user 0m0.124s
  sys 0m0.220s

  [Test Case]

  * Reproducer #1
  $ iptables -F
  $ time (./list-addrs 3000 | xargs -n1 iptables -A FORWARD -j ACCEPT -s)

  * Reproducer #2
  $ iptables -F
  $ time for f in `seq 1 3000` ; do iptables -A FORWARD ; done

  "list-addrs" script can be found here[3]

  [Regression Potential]

   * none expected, the patches have been proven to work on mainline
  kernel, and was reviewed by a few netfilters maintainer + tested by
  myself.

  Reference:
  https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/

  Patches:
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/2394ae21e8b652aff0db1c02e946243c1e2f5edb
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/722d6785e3b29a3b9f95c4d77542a1416094786a
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/18b61e8161cc308cbfd06d2e2c6c0758dfd925ef

  [Other Info]

  * "iptables-restore" doesn't suffer of that netfilter regression, and
  I'm also aware that "iptables-restore" is the favourite approach since
  it is way more efficient than iptables that is executed over and over,
  once for each policy one want to set, but since "binary
  arp/ip/ip6tables" takes vastly longer to perform with that commit, I
  think this need to be address anyway.

  [Related Documents]

  [1] - 
https://github.com/torvalds/linux/commit/71ae0dff02d756e4d2ca710b79f2ff5390029a5f
  [2] - https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c
  [3] - 
https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c#file-list-addrs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640786/+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 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1630238

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+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 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+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 1655420] Re: Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang with a zero window

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1655420

Title:
  Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session
  to hang with a zero window

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

Bug description:
  == Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

  This bug is being mirrored for any distributions that include ibmveth
  large send/receive support.  In short, any distribution with ibmveth
  v1.05 will be affected (releases 14.04.5/Wily+)

  2 upstream commits:

  1. Set GSO size and type
  
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
  2. set GSO segments
  
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

  A VIOS fix is needed as well.

  ---Problem Description---
  When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655420/+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 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: 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/1658491

Title:
  VLAN SR-IOV regression for IXGBE driver

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

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658491/+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 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: 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/1658270

Title:
  Backport Dirty COW patch to prevent wineserver freeze

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a
  backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi
  apps freezing wineserver and leaving it unkillable:

  https://bugs.winehq.org/show_bug.cgi?id=41637

  I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it
  is probably affected.  A patch is available:

  https://lkml.org/lkml/2017/1/5/13
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC2:  jhansonxi   2775 F pulseaudio
   /dev/snd/controlC0:  jhansonxi   2775 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/vg0-lv1 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: dialout
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+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 1640786] Re: netfilter regression introducing a performance slowdown in binary arp/ip/ip6tables

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1640786

Title:
  netfilter regression introducing a performance slowdown in binary
  arp/ip/ip6tables

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

Bug description:
  [SRU JUSTIFICATION]

  [Impact]

  It has been brought to my attention that Ubuntu kernel 4.4 has a
  severe netfilter regression affecting the performance of
  "/sbin/iptables" command, especially when adding large number of
  policies. My source have documented everything here[2].

  Note that the situation can also be reproduce with latest and greatest
  upstream kernel v4.9-rc4.

  I was able to reproduce the situation on my side, and a kernel bisect
  identified the same offending commit[1] as my source found for this
  bug.

  Running the commit right before the offending one have proven to have
  expected performance :

  # commit [71ae0dff] <== Offending commit
  real 0m33.314s
  user 0m1.520s
  sys 0m26.192s

  # commit [d7b59742] <== Right before offending commit
  real 0m5.952s
  user 0m0.124s
  sys 0m0.220s

  [Test Case]

  * Reproducer #1
  $ iptables -F
  $ time (./list-addrs 3000 | xargs -n1 iptables -A FORWARD -j ACCEPT -s)

  * Reproducer #2
  $ iptables -F
  $ time for f in `seq 1 3000` ; do iptables -A FORWARD ; done

  "list-addrs" script can be found here[3]

  [Regression Potential]

   * none expected, the patches have been proven to work on mainline
  kernel, and was reviewed by a few netfilters maintainer + tested by
  myself.

  Reference:
  https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/

  Patches:
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/2394ae21e8b652aff0db1c02e946243c1e2f5edb
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/722d6785e3b29a3b9f95c4d77542a1416094786a
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pablo/nf-next/+/18b61e8161cc308cbfd06d2e2c6c0758dfd925ef

  [Other Info]

  * "iptables-restore" doesn't suffer of that netfilter regression, and
  I'm also aware that "iptables-restore" is the favourite approach since
  it is way more efficient than iptables that is executed over and over,
  once for each policy one want to set, but since "binary
  arp/ip/ip6tables" takes vastly longer to perform with that commit, I
  think this need to be address anyway.

  [Related Documents]

  [1] - 
https://github.com/torvalds/linux/commit/71ae0dff02d756e4d2ca710b79f2ff5390029a5f
  [2] - https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c
  [3] - 
https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c#file-list-addrs

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