[Group.of.nepali.translators] [Bug 1789746] Re: getxattr: always handle namespaced attributes

2018-11-08 Thread Stéphane Graber
** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  getxattr: always handle namespaced attributes

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

Bug description:
  
  == SRU Justification ==
  When running in a container with a user namespace, if you call getxattr
  with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
  silently skips the user namespace fixup that it normally does resulting in
  un-fixed-up data being returned.
  This is caused by posix_acl_fix_xattr_to_user() being passed the total
  buffer size and not the actual size of the xattr as returned by
  vfs_getxattr().

  I have pushed a commit upstream that fixes this bug:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5

  This commit passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  A reproducer for the issue is:

    touch acl_posix

    setfacl -m user:0:rwx acl_posix

  and the compile:

    #define _GNU_SOURCE
    #include 
    #include 
    #include 
    #include 
    #include 
    #include 
    #include 

    /* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
    int main(int argc, void **argv)
    {
    ssize_t ret1, ret2;
    char buf1[128], buf2[132];
    int fret = EXIT_SUCCESS;
    char *file;

    if (argc < 2) {
    fprintf(stderr,
    "Please specify a file with "
    "\"system.posix_acl_access\" permissions set\n");
    _exit(EXIT_FAILURE);
    }
    file = argv[1];

    ret1 = getxattr(file, "system.posix_acl_access",
    buf1, sizeof(buf1));
    if (ret1 < 0) {
    fprintf(stderr, "%s - Failed to retrieve "
    "\"system.posix_acl_access\" "
    "from \"%s\"\n", strerror(errno), file);
    _exit(EXIT_FAILURE);
    }

    ret2 = getxattr(file, "system.posix_acl_access",
    buf2, sizeof(buf2));
    if (ret2 < 0) {
    fprintf(stderr, "%s - Failed to retrieve "
    "\"system.posix_acl_access\" "
    "from \"%s\"\n", strerror(errno), file);
    _exit(EXIT_FAILURE);
    }

    if (ret1 != ret2) {
    fprintf(stderr, "The value of \"system.posix_acl_"
    "access\" for file \"%s\" changed "
    "between two successive calls\n", file);
    _exit(EXIT_FAILURE);
    }

    for (ssize_t i = 0; i < ret2; i++) {
    if (buf1[i] == buf2[i])
    continue;

    fprintf(stderr,
    "Unexpected different in byte %zd: "
    "%02x != %02x\n", i, buf1[i], buf2[i]);
    fret = EXIT_FAILURE;
    }

    if (fret == EXIT_SUCCESS)
    fprintf(stderr, "Test passed\n");
    else
    fprintf(stderr, "Test failed\n");

    _exit(fret);
    }
  and run:

    ./tester acl_posix

  On a non-fixed up kernel this should return something like:

    root@c1:/# ./t
    Unexpected different in byte 16: ffa0 != 00
    Unexpected different in byte 17: ff86 != 00
    Unexpected different in byte 18: 01 != 00

  and on a fixed kernel:

    root@c1:~# ./t
    Test passed

  
  == Fix ==
  82c9a927bc5d ("getxattr: use correct xattr length")

  == Regression Potential ==
  Low.  One liner that passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

2018-11-08 Thread Po-Hsu Lin
4.4.0-139.165 - lowlatency
Regression test CMPL, RTB.

Test case ubuntu_performance_fio_aws does not exist in the database, please 
check
45 / 52 tests were run, missing: ubuntu_bpf_jit, ubuntu_cts_kernel, 
ubuntu_cve_kernel, ubuntu_ecryptfs, ubuntu_ltp_syscalls, ubuntu_zfs_fstest, 
ubuntu_zfs_xfs_generic, xfstests
Issue to note in amd64:
  ubuntu_kvm_unit_tests - 18 failed on gummo
  ubuntu_performance_fio_aws - test for nvidia project, should be skipped
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)

4.4.0-139.165 - generic
Regression test CMPL, RTB.

51 / 52 tests were run, missing: ubuntu_ramfs_stress
Issue to note in amd64:
  ubuntu_kernel_selftests - passed after re-run
  ubuntu_kvm_unit_tests - 32 faile on amaura, 25 failed on michael, 31 failed 
on pepe
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lxc - passed after re-run
  ubuntu_nbd_smoke_test - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - xfs generic/468 timed out

46 / 47 tests were run, missing: xfstests
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-ipi and gicv2-active on starmie pmu on 
ms10-34-mcdivittB0-kernel (bug 1751000)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)

Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - xfs generic/308 timed out, bug 1738152

Issue to note in ppc64le (P8):
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, 
pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 failed with 
X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel 
(bug 1775784) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 
timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - btrfs generic/176 timed out

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_aufs_smoke_test - passed after re-run
  ubuntu_blktrace_smoke_test - passed after re-run
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_docker_smoke_test - passed after re-run
  ubuntu_ecryptfs - passed after re-run
  ubuntu_fan_smoke_test - passed after re-run
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_loop_smoke_test - passed after re-run
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lttng_smoke_test - passed after re-run
  ubuntu_nbd_smoke_test - passed after re-run
  ubuntu_qrt_apparmor - passed after re-run
  ubuntu_qrt_kernel_aslr_collisions - passed after re-run
  ubuntu_qrt_kernel_hardening - passed after re-run
  ubuntu_qrt_kernel_panic - passed after re-run
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  ubuntu_quota_smoke_test - passed after re-run
  ubuntu_squashfs_smoke_test - passed after re-run
  ubuntu_stress_smoke_test - passed after re-run
  ubuntu_zfs_smoke_test - 

[Group.of.nepali.translators] [Bug 1769911] Re: docker.io install fails when docker group exists

2018-11-08 Thread Brian Murray
Hello Michał, or anyone else affected,

Accepted docker.io into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/docker.io/18.06.1-0ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: docker.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: docker.io (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

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

Title:
  docker.io install fails when docker group exists

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  Fix Committed
Status in docker.io source package in Bionic:
  Fix Released
Status in docker.io package in Debian:
  Fix Released

Bug description:
  [impact]
  installation of docker can fail trying to create the docker group if it 
already exists

  [test case]
  # addgroup docker
  # apt install docker.io

  [regression potential]
  The change to fix this but is small and clear: 
https://github.com/tianon/debian-docker/commit/16b582b497a35324246fbb203f2e094d95ec

  Also we don't care much about regressions in docker.io!
  https://wiki.ubuntu.com/DockerUpdates

  [original description]

  After installing nvidia-docker

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: docker.io 17.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May  8 16:22:53 2018
  ErrorMessage: installed docker.io package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-05-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: docker.io
  Title: package docker.io 17.12.1-0ubuntu1 failed to install/upgrade: 
installed docker.io package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1769911/+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 1784602] Re: No option to configure docker.io for restart on package upgrade

2018-11-08 Thread Brian Murray
Hello Tom, or anyone else affected,

Accepted docker.io into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/docker.io/18.06.1-0ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: docker.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: docker.io (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

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

Title:
  No option to configure docker.io for restart on package upgrade

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  Fix Committed
Status in docker.io source package in Bionic:
  Fix Released

Bug description:
  [impact]
  docker.io now prompts on upgrade as to whether to restart, which is an 
improvement, but there is no way to decide ahead of time for a non-interactive 
upgrade.

  [test case]
  # apt-get install docker.io
  # pgrep dockerd
  # dpkg-reconfigure docker.io
  < this will only ask a question once the package from proposed is installed >
  < choose yes >
  # DEBIAN_FRONTEND=noninteractive apt-get install --reinstall docker.io
  # pgrep dockerd
  < check dockerd has restarted >
  # dpkg-reconfigure docker.io
  < choose no >
  # DEBIAN_FRONTEND=noninteractive apt-get install --reinstall docker.io
  # pgrep dockerd
  < check dockerd has not restarted>

  [regression potential]
  The change implementing this clearly only affects install/upgrade scenarios: 
https://github.com/tianon/debian-docker/commit/4bc8afa9594ca51d2707cfbf0cc682e68b215c68.
 The test case above covers these.

  Also we don't care much about regressions in docker.io!
  https://wiki.ubuntu.com/DockerUpdates

  [original description]

  Currently if I run "dpkg-reconfigure docker.io" it doesn't present me
  with any option to restart the package on upgrade. Looking at the
  debian post install file, it should, and lp#1668621 suggests it
  should.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: docker.io 17.03.2-0ubuntu2~16.04.1
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Jul 31 10:15:21 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: docker.io
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1784602/+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 1794396] Re: upgrade to docker 18.06

2018-11-08 Thread Launchpad Bug Tracker
This bug was fixed in the package docker.io - 18.06.1-0ubuntu1~18.04.1

---
docker.io (18.06.1-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to 18.04 (LP: #1794396)

 -- Michael Hudson-Doyle   Thu, 27 Sep 2018
14:39:50 +1200

** Changed in: docker.io (Ubuntu Bionic)
   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/1794396

Title:
  upgrade to docker 18.06

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in docker.io source package in Bionic:
  Fix Released

Bug description:
  [impact]
  we should update docker to the 18.06 release

  [test case]
  The autopkgtests per https://wiki.ubuntu.com/DockerUpdates.

  [regression potential]
  https://wiki.ubuntu.com/DockerUpdates again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1794396/+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 1802341] Re: crash in ENA driver on removing an interface

2018-11-08 Thread Kamal Mostafa
** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

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

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

** Changed in: linux-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Changed in: linux-aws (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Changed in: linux-aws (Ubuntu Cosmic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Changed in: linux-aws (Ubuntu Disco)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1800945] Re: Add Ubuntu disco as as supported release

2018-11-08 Thread Launchpad Bug Tracker
This bug was fixed in the package debootstrap - 1.0.108ubuntu1.1

---
debootstrap (1.0.108ubuntu1.1) cosmic; urgency=medium

  * Add (Ubuntu) disco as a symlink to gutsy. (LP: #1800945)

 -- Brian Murray   Wed, 31 Oct 2018 15:31:00 -0700

** Changed in: debootstrap (Ubuntu Cosmic)
   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/1800945

Title:
  Add Ubuntu disco as as supported release

Status in debootstrap package in Ubuntu:
  Fix Released
Status in debootstrap source package in Trusty:
  Fix Committed
Status in debootstrap source package in Xenial:
  Fix Committed
Status in debootstrap source package in Bionic:
  Fix Committed
Status in debootstrap source package in Cosmic:
  Fix Released

Bug description:
  Add Ubuntu disco 19.04 debootstrap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1800945/+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 1770082] Re: systemd-networkd not renaming devices on boot

2018-11-08 Thread Steve Langasek
The SRU has been rolled back while the fix for the regression is being
prepared.  I still consider the previous SRU verification valid so am
resetting the bug state but not the tags.

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Released => Fix Committed

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 

[Group.of.nepali.translators] [Bug 1800805] Re: linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker

2018-11-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing 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/1800805

Title:
  linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800805/+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 1802330] Re: "Not enough memory" error when trying to work with large images with partclone

2018-11-08 Thread Thomas Ward
** Changed in: partclone (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: partclone (Ubuntu)
   Status: New => Invalid

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

Title:
  "Not enough memory" error when trying to work with large images with
  partclone

Status in partclone package in Ubuntu:
  Invalid
Status in partclone source package in Xenial:
  New

Bug description:
  Partclone is capable of working with images that're fragmented into
  tiny bits, and then reconstructing them and cloning partitions.

  However, with extremely large disks, the version of partclone in
  Xenial has a major flaw: it wants you to have memory equal to the
  'disk size'.

  This means that it can't work properly with creating a raw image file
  from fragmented disk bits.

  This is fixed in later releases, and Bionic and up have 0.3.11 which
  includes a large number of memory improvements which gets rid of these
  'not enough memory' problems.

  This supposedly is also fixed in 0.2.89 per my looking online.

  Note that because of this bug, partclone in Xenial is unusable for
  restoring files or creating raw images from segmented images (such as
  that which Clonezilla takes) when trying to reconstruct the partition
  image.  (Because of this, I am setting "Medium" as the bug
  importance).

  Bionic and later are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1802330/+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 1802330] Re: "Not enough memory" error when trying to work with large images with partclone

2018-11-08 Thread C de-Avillez
** Also affects: partclone (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/1802330

Title:
  "Not enough memory" error when trying to work with large images with
  partclone

Status in partclone package in Ubuntu:
  Invalid
Status in partclone source package in Xenial:
  New

Bug description:
  Partclone is capable of working with images that're fragmented into
  tiny bits, and then reconstructing them and cloning partitions.

  However, with extremely large disks, the version of partclone in
  Xenial has a major flaw: it wants you to have memory equal to the
  'disk size'.

  This means that it can't work properly with creating a raw image file
  from fragmented disk bits.

  This is fixed in later releases, and Bionic and up have 0.3.11 which
  includes a large number of memory improvements which gets rid of these
  'not enough memory' problems.

  This supposedly is also fixed in 0.2.89 per my looking online.

  Note that because of this bug, partclone in Xenial is unusable for
  restoring files or creating raw images from segmented images (such as
  that which Clonezilla takes) when trying to reconstruct the partition
  image.  (Because of this, I am setting "Medium" as the bug
  importance).

  Bionic and later are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1802330/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2018-11-08 Thread Marc Deslauriers
** Changed in: openssh (Ubuntu Cosmic)
   Status: In Progress => Fix Released

** Changed in: openssh (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/1794629

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1615381] Re: apt-get autoremove may remove current kernel

2018-11-08 Thread Balint Reczey
** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1799408] Re: linux-kvm: 4.4.0-1037.43 -proposed tracker

2018-11-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   verification-testing: Testing 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/1799408

Title:
  linux-kvm: 4.4.0-1037.43 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-11-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
-   verification-testing: Testing 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/1801124

Title:
  linux-aws: 4.4.0-1072.82 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress

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

2018-11-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   verification-testing: Testing 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/1799410

Title:
  linux-snapdragon: 4.4.0-1104.109 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-11-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   verification-testing: Testing 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/1799409

Title:
  linux-raspi2: 4.4.0-1100.108 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

2018-11-08 Thread Kleber Sacilotto de Souza
Verification tests completed with the following exceptions:
- bug 1775068: Xenial is not the original series used by the bug reporter.
- bug 1797314: fix verified with Bionic, reporter doesn't have a Xenial setup 
for verification.

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => 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/1799401

Title:
  linux: 4.4.0-139.165 -proposed tracker

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

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

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

  backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial)
  derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 
(linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
snap-certification-testing: Ready
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+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 1787120] Re: apt show fails to show large records

2018-11-08 Thread Bug Watch Updater
** Changed in: apt (Debian)
   Status: Confirmed => 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/1787120

Title:
  apt show fails to show large records

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt show can't show records that are larger than 32 KB, e.g. records with 
long lists of provides

  [Test case]
  A test case is provided in autopkgtest, hence validates automatically. See 
https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df
 for details.

  [Other info]
  This is a duplicate of Debian bug #905527.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+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 1744166] Re: East-Saskatchewan timezone removed in latest tzdata

2018-11-08 Thread Bug Watch Updater
** Changed in: php-sabre-vobject-3 (Debian)
   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/1744166

Title:
  East-Saskatchewan timezone removed in latest tzdata

Status in php-sabre-vobject-3 package in Ubuntu:
  Fix Released
Status in php-sabre-vobject-3 source package in Xenial:
  Fix Released
Status in php-sabre-vobject-3 source package in Artful:
  Won't Fix
Status in php-sabre-vobject-3 package in Debian:
  Fix Released

Bug description:
  [Impact]

  * DEP8 tests for php-sabre-vobject-3 currently fail in 16.04 because
  the 2017c version of tzdata dropped the East-Saskatchewan timezone,
  which is hardcoded in the package.

  * This in turn blocks SRUs of new PHP7.0 microreleases.

  [Test Case]

  * Run the autopkgtests for this source package before and after the
  change. They should pass after.

  [Regression Potential]

  * None, this timezone is no longer valid in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-sabre-vobject-3/+bug/1744166/+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 1801900] Re: Xenial update: 4.4.162 upstream stable release

2018-11-08 Thread Stefan Bader
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1801900

Title:
  Xenial update: 4.4.162 upstream stable release

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

Bug description:
  
  SRU Justification

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

 4.4.162 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.162
  HV: properly delay KVP packets when negotiation is in progress
  Drivers: hv: kvp: fix IP Failover
  Drivers: hv: util: Pass the channel information during the init call
  Drivers: hv: utils: Invoke the poll function after handshake
  usb: gadget: serial: fix oops when data rx'd after close
  ARC: build: Get rid of toolchain check
  powerpc/tm: Avoid possible userspace r1 corruption on reclaim
  powerpc/tm: Fix userspace r13 corruption
  net/mlx4: Use cpumask_available for eq->affinity_mask
  Input: atakbd - fix Atari CapsLock behaviour
  Input: atakbd - fix Atari keymap
  clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for 
non-am43 SoCs
  media: af9035: prevent buffer overflow on write
  x86/fpu: Finish excising 'eagerfpu'
  x86/fpu: Remove struct fpu::counter
  x86/fpu: Remove use_eager_fpu()
  KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch
  rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096
  net: systemport: Fix wake-up interrupt race during resume
  net: mvpp2: Extract the correct ethtype from the skb for tx csum offload
  team: Forbid enslaving team device to itself
  qlcnic: fix Tx descriptor corruption on 82xx devices
  net/usb: cancel pending work when unbinding smsc75xx
  netlabel: check for IPV4MASK in addrinfo_get
  net/ipv6: Display all addresses in output of /proc/net/if_inet6
  net: ipv4: update fnhe_pmtu when first hop's MTU changes
  ipv4: fix use-after-free in ip_cmsg_recv_dstaddr()
  ip_tunnel: be careful when accessing the inner header
  ip6_tunnel: be careful when accessing the inner header
  bonding: avoid possible dead-lock
  bnxt_en: Fix TX timeout during netpoll.
  jffs2: return -ERANGE when xattr buffer is too small
  xhci: Don't print a warning when setting link state for disabled ports
  i2c: i2c-scmi: fix for i2c_smbus_write_block_data
  perf script python: Fix export-to-postgresql.py occasional failure
  mach64: detect the dot clock divider correctly on sparc
  mm/vmstat.c: fix outdated vmstat_text
  ext4: add corruption check in ext4_xattr_set_entry()
  drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7
  ARM: dts: at91: add new compatibility string for macb on sama5d3
  net: macb: disable scatter-gather for macb on sama5d3
  stmmac: fix valid numbers of unicast filter entries
  sound: enable interrupt after dma buffer initialization
  mfd: omap-usb-host: Fix dts probe of children
  selftests/efivarfs: add required kernel configs
  ASoC: sigmadsp: safeload should not have lower byte limit
  ASoC: wm8804: Add ACPI support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801900/+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 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags

2018-11-08 Thread Stefan Bader
Already included in Ubuntu-4.4.0-138.164 in updates/security.

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

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

Title:
  [Ubuntu] qdio: reset old sbal_state flags

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==

  Description: qdio: reset old sbal_state flags

  Symptom:
     af_iucv socket using HiperSockets may stall.
  Problem:
     When allocating a new AOB fails, handle_outbound() is
  still capable of transmitting the selected buffer
  (just without async completion).
  But if a previous transfer on this queue slot used
  async completion, its sbal_state flags field is still set
  to QDIO_OUTBUF_STATE_FLAG_PENDING.
  So when the upper layer driver sees this stale flag, it
  expects an async completion that never happens.
  Solution:
     Unconditionally clear the buffer's flags field.

  == Fix ==

  64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
  sbal_state flags")

  == Regression Potential ==

  Low, because:
  - s390x only
  - further limited to qeth driver (OSA Express networking)
  - changes are limited to two files and 6 lines
     - arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
     - drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
  - error was identified at IBM/customer, fix was created there and tested 
upfront
  - (changes are upstream in 4.20 (according to bug description,
 but in 4.19 according to 'git tag'),
 hence will make it automatically into 'disco')

  == Test Case ==

  Test case / reproduction:
  Error inject and then simulate out-of-memory situation.

  __

  Description:  qdio: reset old sbal_state flags

  Symptom:  af_iucv socket using HiperSockets may stall.

  Problem:  When allocating a new AOB fails, handle_outbound() is
    still capable of transmitting the selected buffer
    (just without async completion).
    But if a previous transfer on this queue slot used
    async completion, its sbal_state flags field is still set
    to QDIO_OUTBUF_STATE_FLAG_PENDING.
    So when the upper layer driver sees this stale flag, it
    expects an async completion that never happens.

  Solution: Unconditionally clear the buffer's flags field.

  Reproduction: Error inject, simulating out-of-memory.

  kernel 4.20
  Upstream-ID:  64e03ff72623b8c2ea89ca3cb660094e019ed4ae

  Canonical , please provide this fix for all Releases in Service
  Ubuntu 18.10, 18.04 and 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+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 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags

2018-11-08 Thread Stefan Bader
Already in Ubuntu-4.18.0-8.9.

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

** Changed in: linux (Ubuntu Disco)
   Status: New => 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/1801686

Title:
  [Ubuntu] qdio: reset old sbal_state flags

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==

  Description: qdio: reset old sbal_state flags

  Symptom:
     af_iucv socket using HiperSockets may stall.
  Problem:
     When allocating a new AOB fails, handle_outbound() is
  still capable of transmitting the selected buffer
  (just without async completion).
  But if a previous transfer on this queue slot used
  async completion, its sbal_state flags field is still set
  to QDIO_OUTBUF_STATE_FLAG_PENDING.
  So when the upper layer driver sees this stale flag, it
  expects an async completion that never happens.
  Solution:
     Unconditionally clear the buffer's flags field.

  == Fix ==

  64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
  sbal_state flags")

  == Regression Potential ==

  Low, because:
  - s390x only
  - further limited to qeth driver (OSA Express networking)
  - changes are limited to two files and 6 lines
     - arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
     - drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
  - error was identified at IBM/customer, fix was created there and tested 
upfront
  - (changes are upstream in 4.20 (according to bug description,
 but in 4.19 according to 'git tag'),
 hence will make it automatically into 'disco')

  == Test Case ==

  Test case / reproduction:
  Error inject and then simulate out-of-memory situation.

  __

  Description:  qdio: reset old sbal_state flags

  Symptom:  af_iucv socket using HiperSockets may stall.

  Problem:  When allocating a new AOB fails, handle_outbound() is
    still capable of transmitting the selected buffer
    (just without async completion).
    But if a previous transfer on this queue slot used
    async completion, its sbal_state flags field is still set
    to QDIO_OUTBUF_STATE_FLAG_PENDING.
    So when the upper layer driver sees this stale flag, it
    expects an async completion that never happens.

  Solution: Unconditionally clear the buffer's flags field.

  Reproduction: Error inject, simulating out-of-memory.

  kernel 4.20
  Upstream-ID:  64e03ff72623b8c2ea89ca3cb660094e019ed4ae

  Canonical , please provide this fix for all Releases in Service
  Ubuntu 18.10, 18.04 and 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+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 1801893] Re: Xenial update: 4.4.161 upstream stable release

2018-11-08 Thread Stefan Bader
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Xenial update: 4.4.161 upstream stable release

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

Bug description:
  SRU Justification

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

     4.4.161 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly
  * fbdev/omapfb: fix omapfb_memory_read infoleak
  * x86/vdso: Fix asm constraints on vDSO syscall fallbacks
  * x86/vdso: Fix vDSO syscall fallback asm constraint regression
  * PCI: Reprogram bridge prefetch registers on resume
  * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys
  * PM / core: Clear the direct_complete flag on errors
  * dm cache: fix resize crash if user doesn't reload cache table
  * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI
  * USB: serial: simple: add Motorola Tetra MTP6550 id
  * of: unittest: Disable interrupt node tests for old world MAC systems
  * ext4: always verify the magic number in xattr blocks
  * cgroup: Fix deadlock in cpu hotplug path
  * ath10k: fix use-after-free in ath10k_wmi_cmd_send_nowait
  * powerpc/fadump: Return error when fadump registration fails
  * ARC: clone syscall to setp r25 as thread pointer
  * ucma: fix a use-after-free in ucma_resolve_ip()
  * ubifs: Check for name being NULL while mounting
  * tcp: increment sk_drops for dropped rx packets
  * tcp: use an RB tree for ooo receive queue
  * tcp: fix a stale ooo_last_skb after a replace
  * tcp: free batches of packets in tcp_prune_ofo_queue()
  * tcp: call tcp_drop() from tcp_data_queue_ofo()
  * tcp: add tcp_ooo_try_coalesce() helper
  * ath10k: fix scan crash due to incorrect length calculation
  * ebtables: arpreply: Add the standard target sanity check
  * Linux 4.4.161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801893/+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 1799426] Re: linux-hwe-edge: 4.15.0-39.42~16.04.1 -proposed tracker

2018-11-08 Thread Po-Hsu Lin
4.15.0-39.42~16.04.1 - lowlatency
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 29 failed on amaura, 13 failed on michael, 25 failed 
on pepe
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - btrfs generic/176 timed out, xfs generic/438 timed out

33 / 46 tests were run, missing: ubuntu_aufs_smoke_test, 
ubuntu_blktrace_smoke_test, ubuntu_docker_smoke_test, ubuntu_fan_smoke_test, 
ubuntu_kvm_smoke_test, ubuntu_loop_smoke_test, ubuntu_lttng_smoke_test, 
ubuntu_nbd_smoke_test, ubuntu_quota_smoke_test, ubuntu_squashfs_smoke_test, 
ubuntu_stress_smoke_test, ubuntu_sysdig_smoke_test, ubuntu_zram_smoke_test
Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - xfs generic/112 timed out

4.15.0-39.42~16.04.1 - generic
Regression test CMPL, RTB.
 to note in amd64:
  ubuntu_kvm_unit_tests - 29 failed on amaura, 13 failed on michael, 25 failed 
on pepe
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - btrfs generic/176 timed out, xfs generic/463 timed out

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-ipi on moonshots gicv2-mmio-up on moonshots 
gicv2-mmio-3p on moonshots pmu on starmie (bug 1751000) gicv2-ipi on thunderX 
gicv2-mmio on thunderX gicv2-mmio-up on thunderX gicv2-mmio-3p on thunderX 
gicv2-active on thunderX timer on thunderX
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_zfs_xfs_generic - passed after re-run
  xfstests - btrfs generic/176 timed out

45 / 46 tests were run, missing: xfstests
Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test

Test case ubuntu_sysdig_smoke_test, ubuntu_vfat_stress does not exist in the 
database, please check
Issue to note in ppc64le (P8):
  hwclock - failed with small difference on one node
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1755118)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) fallocate05 (bug 
1783880) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 
(bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_sysdig_smoke_test - DKMS failed to build on B-4.18 and X-4.15 (bug 
1802240)
  xfstests - btrfs generic/176 timed out

Note: the missing smoke test in i386 lowlatency is caused by bug 1793464

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-hwe-edge: 4.15.0-39.42~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the  

[Group.of.nepali.translators] [Bug 1799425] Re: linux-hwe: 4.15.0-39.42~16.04.1 -proposed tracker

2018-11-08 Thread Po-Hsu Lin
4.15.0-39.42~16.04.1 - lowlatency
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 29 failed on amaura, 13 failed on michael, 25 failed 
on pepe
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - btrfs generic/176 timed out, xfs generic/438 timed out

33 / 46 tests were run, missing: ubuntu_aufs_smoke_test, 
ubuntu_blktrace_smoke_test, ubuntu_docker_smoke_test, ubuntu_fan_smoke_test, 
ubuntu_kvm_smoke_test, ubuntu_loop_smoke_test, ubuntu_lttng_smoke_test, 
ubuntu_nbd_smoke_test, ubuntu_quota_smoke_test, ubuntu_squashfs_smoke_test, 
ubuntu_stress_smoke_test, ubuntu_sysdig_smoke_test, ubuntu_zram_smoke_test
Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - xfs generic/112 timed out

4.15.0-39.42~16.04.1 - generic
Regression test CMPL, RTB.
 to note in amd64:
  ubuntu_kvm_unit_tests - 29 failed on amaura, 13 failed on michael, 25 failed 
on pepe
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  xfstests - btrfs generic/176 timed out, xfs generic/463 timed out

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-ipi on moonshots gicv2-mmio-up on moonshots 
gicv2-mmio-3p on moonshots pmu on starmie (bug 1751000) gicv2-ipi on thunderX 
gicv2-mmio on thunderX gicv2-mmio-up on thunderX gicv2-mmio-3p on thunderX 
gicv2-active on thunderX timer on thunderX
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_zfs_xfs_generic - passed after re-run
  xfstests - btrfs generic/176 timed out

45 / 46 tests were run, missing: xfstests
Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) inotify08 failed with 
X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 (bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test

Test case ubuntu_sysdig_smoke_test, ubuntu_vfat_stress does not exist in the 
database, please check
Issue to note in ppc64le (P8):
  hwclock - failed with small difference on one node
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1755118)
  ubuntu_ltp_syscalls - execveat03 failed (bug 1786729) fallocate05 (bug 
1783880) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) statx05 
(bug 1798524)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_sysdig_smoke_test - DKMS failed to build on B-4.18 and X-4.15 (bug 
1802240)
  xfstests - btrfs generic/176 timed out

Note: the missing smoke test in i386 lowlatency is caused by bug 1793464

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-hwe: 4.15.0-39.42~16.04.1 -proposed tracker

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