[Group.of.nepali.translators] [Bug 1842562] Re: AWS: Add udev rule to set Instance Store device IO timeouts
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: cloud-init (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: cloud-init (Ubuntu Bionic)
Status: In Progress => 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/1842562
Title:
AWS: Add udev rule to set Instance Store device IO timeouts
Status in cloud-init package in Ubuntu:
Won't Fix
Status in cloud-init source package in Xenial:
Won't Fix
Status in cloud-init source package in Bionic:
Won't Fix
Status in cloud-init source package in Disco:
Won't Fix
Status in cloud-init source package in Eoan:
Won't Fix
Bug description:
[Impact]
AWS wish to implement per-device IO timeouts in their cloud, since
currently NVMe devices only support a single global timeout, and this
doesn't play well with EBS volumes, which have error recovery
capabilities built into the back end, and require large timeouts, and
Instance Store / ephemeral volumes, which are to be treated as local
disks, which require short timeouts.
AWS have proposed a solution which is to backport the below two
patches to the Ubuntu kernels:
commit 65cd1d13b880920054d6c750679baa80b7f9c072
Author: Weiping Zhang
Date: Thu Nov 29 00:04:39 2018 +0800
subject: block: add io timeout to sysfs
commit 4d25339e32a1b6e1f490bb78b1e5b0fa9eb3e073
Author: Weiping Zhang
Date: Tue Apr 2 21:14:30 2019 +0800
subject: block: don't show io_timeout if driver has no timeout handler
This enables a sysfs entry in /sys/block/nvmeXnX/queue/io_timeout
which gets and sets the io_timeout per device in milliseconds.
Kernel commits are being tracked in LP #1841461
EBS volumes will use the default timeout as set on the kernel command
line of 4294966296, and Instance Store volumes will need to use a
default timeout of 3.
AWS have suggested that we deploy the below udev rule to automatically
set the io_timeout of all Instance Store volumes to 3:
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
This bug is to add the above udev rule to cloud-init.
[Test Case]
This requires an AWS instance that has Instance Store volumes
configured, and I suggest using c5d.large instances.
I have built a test kernel for bionic linux-aws, version
4.15.0-1043.45+hf240347v20190828b2 which is available from here:
https://launchpad.net/~mruffell/+archive/ubuntu/sf240347-kernel
Install the kernel with the below:
1) sudo add-apt-repository ppa:mruffell/sf240347-kernel
2) sudo apt-get update
Modify grub to boot it, this kernel is 1043, and current is 1044, so
it will likely be "1>2" in grub config:
3) sudo vim /etc/default/grub
Change GRUB_DEFAULT=0 to GRUB_DEFAULT="1>2"
4) sudo update-grub
5) reboot
Once system is up, check kernel version:
6) uname -rv
4.15.0-1043-aws #45+hf240347v20190828b2-Ubuntu SMP Wed Aug 28 06:08:21 UTC
2019
Verify that we have two nvme disks, one EBS and one Instance Store:
7) lsblk
Should have two disks, normally nvme0 and nvme1.
See what device is what:
8) sudo udevadm info --attribute-walk /dev/nvme0
For me, ATTR{model} is "Amazon Elastic Block Store"
9) sudo udevadm info --attribute-walk /dev/nvme1
For me, ATTR{model} is "Amazon EC2 NVMe Instance Storage"
Look at the two timeouts (Note no udev rule yet):
10) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
4294966296
Now we deploy the udev rule:
Place the following line in /lib/udev/rules.d/66-aws-io-timeout.rules
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
Now trigger udev rules:
11) sudo udevadm trigger
Look at the timeouts now:
12) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
3
[Regression Potential]
Regression potential is low since we are adding a udev rule which
applies only to AWS instances, and only for instances which support
Instance Store devices.
The only thing being modified is the device timeout and the udev rule
is robust to device reordering as it goes by model attr information.
When the udev rule is used with unpatched kernels, nothing happens
since the sysfs entry does not exist, and no errors or the like are
reported.
[Other Info]
cloud-init appears to carry azure specific udev rules, which makes me think
that cloud-init is the right place for this requested udev rule to live.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1842562/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
[Group.of.nepali.translators] [Bug 1890667] Re: xenial/linux-fips: 4.4.0-1045.50 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Tuesday, 18. August 2020 20:07 UTC + phase: Testing + phase-changed: Tuesday, 18. August 2020 20:17 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Stalled -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1045.50 meta: 4.4.0.1045.47 signed: 4.4.0-1045.50 -- 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/1890667 Title: xenial/linux-fips: 4.4.0-1045.50 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Tuesday, 18. August 2020 20:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1045.50 meta: 4.4.0.1045.47 signed: 4.4.0-1045.50 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1890667/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws (Ubuntu Eoan) Status: Triaged => 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Triaged Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Triaged Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-4.15 source package in Eoan: Invalid Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1864174] Re: rustc 1.41 and cargo 0.42 required by firefox 75
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: rustc (Ubuntu Eoan) Status: Fix Committed => 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/1864174 Title: rustc 1.41 and cargo 0.42 required by firefox 75 Status in cargo package in Ubuntu: Fix Released Status in rustc package in Ubuntu: Fix Released Status in cargo source package in Xenial: Fix Released Status in rustc source package in Xenial: Fix Committed Status in cargo source package in Bionic: Fix Released Status in rustc source package in Bionic: Fix Committed Status in cargo source package in Eoan: Fix Released Status in rustc source package in Eoan: Won't Fix Bug description: Firefox 75+ will require rustc 1.41 and cargo 0.42 to build¹. The beta phase for Firefox 75.0 begins on 2020-03-05 and release candidates will be available from 2020-04-02. We will need these in focal and all supported releases (xenial, bionic and eoan). ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1615003 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1864174/+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 1828258] Re: ldirectord systemd service fails if no /var/lock/subsys dir
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: resource-agents (Ubuntu Eoan) Status: In Progress => 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/1828258 Title: ldirectord systemd service fails if no /var/lock/subsys dir Status in resource-agents package in Ubuntu: In Progress Status in resource-agents source package in Xenial: In Progress Status in resource-agents source package in Bionic: In Progress Status in resource-agents source package in Cosmic: In Progress Status in resource-agents source package in Disco: Won't Fix Status in resource-agents source package in Eoan: Won't Fix Bug description: [impact] ldirectord's systemd service script contains commands to touch and remove a file in the /var/lock/subsys directory; however, locks there are a SysV service serialization thing, and are unneeded with systemd. It's unclear why the ldirectord systemd service script contains the lines, but they come from upstream so we should get it fixed there and then correct debian and ubuntu. this impacts users because if no /var/lock/subsys directory exists, the systemd service will fail to start, which can impact installing or upgrading the resource-agents package. [test case] remove the /var/lock/subsys directory and try to install or upgrade ldirectord: ubuntu@lp1828258:~$ sudo rmdir /var/lock/subsys ubuntu@lp1828258:~$ sudo apt install ldirectord Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt autoremove' to remove it. The following NEW packages will be installed: ldirectord 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/62.1 kB of archives. After this operation, 233 kB of additional disk space will be used. Selecting previously unselected package ldirectord. (Reading database ... 30382 files and directories currently installed.) Preparing to unpack .../ldirectord_1%3a4.2.0-1ubuntu1_all.deb ... Unpacking ldirectord (1:4.2.0-1ubuntu1) ... Setting up ldirectord (1:4.2.0-1ubuntu1) ... ...(120 second or so delay)... Job for ldirectord.service failed because the control process exited with error code. See "systemctl status ldirectord.service" and "journalctl -xe" for details. invoke-rc.d: initscript ldirectord, action "start" failed. ● ldirectord.service - Monitor and administer real servers in a LVS cluster of load balanced virtual servers Loaded: loaded (/lib/systemd/system/ldirectord.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-05-09 11:27:53 UTC; 11ms ago Docs: man:ldirectord(8) Process: 7559 ExecStart=/usr/sbin/ldirectord start (code=exited, status=0/SUCCESS) Process: 7564 ExecStartPost=/usr/bin/touch /var/lock/subsys/ldirectord (code=exited, status=1/FAILURE) Process: 7565 ExecStopPost=/bin/rm -f /var/lock/subsys/ldirectord (code=exited, status=0/SUCCESS) Main PID: 7561 Tasks: 3 (limit: 4915) Memory: 71.7M CGroup: /system.slice/ldirectord.service ├─2547 /usr/bin/perl -w /usr/sbin/ldirectord start ├─7078 /usr/bin/perl -w /usr/sbin/ldirectord start └─7561 /usr/bin/perl -w /usr/sbin/ldirectord start May 09 11:26:22 lp1828258 systemd[1]: Starting Monitor and administer real servers in a LVS cluster of load balanced virtual servers... May 09 11:26:23 lp1828258 systemd[1]: ldirectord.service: Supervising process 7561 which is not our child. We'll most likely not notice when it exits. May 09 11:26:23 lp1828258 touch[7564]: /usr/bin/touch: cannot touch '/var/lock/subsys/ldirectord': No such file or directory [regression potential] if something internal to resource-agents actually uses the old SysV- style /var/lock/subsys lock, removing it could cause a regression. However, it shouldn't, because the lock was for use only by SysV service scripts. Also, as we should fix this upstream first, they should know if it is used for any other purpose, so if they accept the change it should be safe. [other info] this is causing autopkgtest failures, especially on arm; but the failure could happen on any arch. also note that /var/lock/subsys (where /var/lock/ is a symlink to /run/lock) is managed by systemd's tmpfiles, as a 'legacy' directory: ubuntu@lp1828258:~$ cat /usr/lib/tmpfiles.d/legacy.conf ...[snip]... # These files are considered legacy and are unnecessary on legacy-free # systems. L /var/lock - - - - ../run/lock # /run/lock/subsys is used for serializing SysV service execution, and # hence without use on SysV-less
[Group.of.nepali.translators] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gcp (Ubuntu Eoan) Status: Triaged => 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Triaged Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Triaged Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-4.15 source package in Eoan: Invalid Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1842479] Re: timer_create will fail with invalid error code
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => 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/1842479 Title: timer_create will fail with invalid error code Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: [Impact] On some OpenPower systems, RTC does not support set_alarm, and timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of EOPNOTSUPP. This will break some regression testing that expects the later value. [Test cases] Run LTP syscalls regression testing, which we do before releasing kernels. [Regression potential] This should not break any userspace, as none should be using/expecting ENOTSUPP for any call. In order to do so, they would have to go out of their way as it's not defined on libc headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+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 1870555] Re: SSH authentication fails for many clients due to receiving of SSH_MSG_IGNORE packet
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: proftpd (Ubuntu Eoan) Status: Incomplete => 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/1870555 Title: SSH authentication fails for many clients due to receiving of SSH_MSG_IGNORE packet Status in proftpd package in Ubuntu: Fix Released Status in proftpd source package in Xenial: Incomplete Status in proftpd source package in Bionic: Incomplete Status in proftpd source package in Eoan: Won't Fix Bug description: This bug has been brought to my attention the following: There is a Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622 The proftpd-basic package suffers from this bug. The impact is very widespread. Every person that uses Filezilla client version greater than 3.46.1 cannot connect to any Ubuntu server using this proftpd package due to the bug. As you see in the link above, there is a patch for Debian. So is it possible that the support team can get this functionality bug and security fix implemented in Xenial and Bionic? https://github.com/proftpd/proftpd/commit/3d17c8419afb10580b942f392f0a5c6de995c4e2 # Proftpd $ git describe --contains 3d17c8419 v1.3.7rc3~25^2 proftpd-basic | 1.3.5a-1ubuntu0.1 | xenial-updates/universe proftpd-basic | 1.3.5e-1build1 | bionic/universe proftpd-basic | 1.3.6-4| disco/universe proftpd-basic | 1.3.6-6build2 | eoan/universe proftpd-basic | 1.3.6c-2 | focal/universe Focal has the patch already: ./f/proftpd-dfsg-1.3.6c/debian/patches/upstream_4385 # Filezilla filezilla | 3.15.0.2-1ubuntu1 | xenial/universe filezilla | 3.28.0-1 | bionic/universe filezilla | 3.39.0-2 | disco/universe filezilla | 3.39.0-2 | eoan/universe filezilla | 3.46.3-1build1| focal/universe Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622 http://bugs.proftpd.org/show_bug.cgi?id=4385 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/proftpd/+bug/1870555/+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 1879327] Re: Enforce all config annotations
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => 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/1879327 Title: Enforce all config annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Not all config annotations are enforced, which means config could regress without notice. [Test case] Check the logs mention much more options being enforced. From the hundreds to more than 1. [Regression potential] Builds will start failing when config doesn't match annotations. However, this is an opt-in for now, which means only those branches prepared to accept it will risk such regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: systemd (Ubuntu Eoan) Status: Confirmed => 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Won't Fix Status in systemd package in Debian: Fix Released Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1845048] Re: Improve sysctl handling on kdump-tools
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Eoan) Status: In Progress => 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/1845048 Title: Improve sysctl handling on kdump-tools Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: In Progress Status in makedumpfile package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1845048/+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 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: corosync (Ubuntu Eoan) Status: Triaged => 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/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Triaged Status in corosync source package in Bionic: Triaged Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Won't Fix Status in corosync source package in Focal: Fix Released Bug description: A /etc/init.d/corosync-notifyd contains two definitions for the PIDFILE: > PIDFILE=/var/run/$NAME.pid > SCRIPTNAME=/etc/init.d/$NAME > PIDFILE=/var/run/corosync.pid The first one is correct and the second one is wrong as it refers to the corosync service's pidfile instead The corosync package version is 2.3.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+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 1710278] Re: [2.3a1] named stuck on reload, DNS broken
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: bind9 (Ubuntu Eoan) Status: In Progress => 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/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Released Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Released Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: Won't Fix Status in bind9 source package in Eoan: Won't Fix Bug description: [Impact] * systemd thinks the service is running, but it does not respond to any commands or requests. Also, it doesn't respond to signals other than kill -9. service restarts hang, rndc hangs. * being that the deadlock is in bind9 that ships in bionic the issue needs to be backported to 2.4.3 so MAAS from the archive in bionic can handle the deadlock and get bind9 unstuck. * change in MAAS watches for this case to occur with bind9, then MAAS will force kill the service and restart it. [Test Case] * very hard to reproduce but the issue occurs when bind9 deadlocks, it response to nothing over the network or rndc. SIGTERM does not kill it only SIGKILL works to force kill the process and get systemd to restart it. [Regression Potential] * possible that bind9 will not be started correctly or possible that bind9 will be placed into a forever restart loop To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+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 1638210] Re: saidar segmentation fault
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: libstatgrab (Ubuntu Eoan) Status: Incomplete => 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/1638210 Title: saidar segmentation fault Status in libstatgrab package in Ubuntu: Fix Released Status in libstatgrab source package in Xenial: Incomplete Status in libstatgrab source package in Bionic: Incomplete Status in libstatgrab source package in Eoan: Won't Fix Status in libstatgrab package in Debian: Fix Released Bug description: Erreur de segmentation (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+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 1831940] Re: hibernation support for linux-aws
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws-5.0 (Ubuntu Eoan) Status: Confirmed => 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/1831940 Title: hibernation support for linux-aws Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.0 package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Status in linux-aws-5.0 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-aws-5.0 source package in Bionic: Fix Released Status in linux-aws source package in Disco: Won't Fix Status in linux-aws-5.0 source package in Disco: Invalid Status in linux-aws source package in Eoan: Fix Released Status in linux-aws-5.0 source package in Eoan: Won't Fix Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.0 source package in Focal: Invalid Bug description: Additional AWS-specific and mainline patches are required to support hibernation across the various types of AWS instances. The following patch sets for linux-aws-xenial and linux-aws-bionic provide the necessary functionality, and should only impact the hibernation and resume paths. [linux-aws-xenial] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. radix-tree: delete radix_tree_locate_item() mm: rid swapoff of quadratic complexity sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to wake_up() sched/wait: Avoid abort_exclusive_wait() in ___wait_event() sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock() sched/wait: Introduce init_wait_entry() sched/wait: Standardize wait_bit_queue naming sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled NVMe: Allow request merges PM / hibernate: Do not free preallocated safe pages during image restore PM / hibernate: Recycle safe pages after image restoration PM / hibernate: Simplify mark_unsafe_pages() UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on hibernate [linux-aws-bionic] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. mm: rid swapoff of quadratic complexity sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff netlink: Don't shift on 64 for ngroups [linux-aws-edge-bionic] UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing PM / hibernate: memory_bm_find_bit(): Tighten node optimisation mm: rid swapoff of quadratic complexity mm: refactor swap-in logic out of shmem_getpage_gfp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1831940/+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 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Eoan) Status: Confirmed => 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/1800873 Title: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command- line Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Currently kdump has an useful option to append parameters to the kdump kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a reciprocal option which users could use to remove parameters without needing to rewrite the whole line. The option name proposed here is KDUMP_CMDLINE_REMOVE, which would tentatively "sed"-out the options from the kernel command-line before appending the new ones from KDUMP_CMDLINE_APPEND. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800873/+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 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: corosync (Ubuntu Eoan) Status: Confirmed => 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/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Trusty: Won't Fix Status in corosync source package in Xenial: Confirmed Status in corosync source package in Zesty: Won't Fix Status in corosync source package in Bionic: Confirmed Status in corosync source package in Disco: Won't Fix Status in corosync source package in Eoan: Won't Fix Status in corosync source package in Focal: Fix Released Bug description: [Environment] Ubuntu Xenial 16.04 Amd64 [Test Case] 1) sudo apt-get install corosync 2) sudo corosync-blackbox. root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black /usr/bin/corosync-blackbox Expected results: corosync-blackbox runs OK. Current results: $ sudo corosync-blackbox /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found [Impact] * Cannot run corosync-blackbox [Regression Potential] * None identified. [Fix] Make the package dependant of libqb-dev root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep qb-bl /usr/sbin/qb-blackbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+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 1845687] Re: memory test in ubuntu_kvm_unit tests fails Xenial linux-kvm
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-kvm (Ubuntu Eoan) 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/1845687 Title: memory test in ubuntu_kvm_unit tests fails Xenial linux-kvm Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Eoan: Won't Fix Bug description: Series: Xenial Kernel: 4.4.0-1059.66 linux-kvm specifically clfushopt and clwb 09/23 08:43:08 DEBUG| utils:0116| Running 'kvm-ok' 09/23 08:43:08 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists 09/23 08:43:08 DEBUG| utils:0153| [stdout] KVM acceleration can be used 09/23 08:43:08 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory' 09/23 08:43:08 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4 09/23 08:43:09 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.HnxXwZrpQ9 -smp 1 -cpu host # -initrd /tmp/tmp.SL7FtNHKpq 09/23 08:43:09 DEBUG| utils:0153| [stdout] enabling apic 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: clflush (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: sfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: lfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: mfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clflushopt (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clwb (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: invalid clwb 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: pcommit (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] SUMMARY: 8 tests, 2 unexpected failures 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845687/+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 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => 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/1864092 Title: quotactl07 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: 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 Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: == SRU Justification == This quotactl07 is a new test case added in LTP test suite, The test will fail with: <<>> incrementing stop tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 == Fix == * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) Focal got this patch from stable update. This patch can be cherry- picked into all the other kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/ All patched kernels are working as expected, == Regression Potential == Low, change limited to quota on XFS, and it's just adding a check for the flags. == Original Bug Report == Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+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 1882180] Re: DoS vulnerability: fail to allocate
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: whoopsie (Ubuntu Eoan) Status: Confirmed => 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/1882180 Title: DoS vulnerability: fail to allocate Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Bionic: Fix Released Status in whoopsie source package in Eoan: Won't Fix Status in whoopsie source package in Focal: Fix Released Status in whoopsie source package in Groovy: Fix Released Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in the parse_report function. A crafted input, i.e., crash report located in '/var/crash/', will lead to a denial of service attack. During the parsing of the crash report, the data length is not checked. The value of data length can be directly controlled by an input file. In the parse_report() function, the g_malloc or g_realloc is called based on data length. If we set the value of data length close to the amount of system memory, it will cause the daemon process to terminate unexpectedly, hang the system, or trigger the OOM killer. # PoC Please check the below whoopsie_killer2.py Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1880832] Re: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: wslu (Ubuntu Eoan) 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/1880832 Title: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Eoan: Won't Fix Bug description: [Impact] The package is already released in focal/groovy but it still affects eoan/bionic/xenial, a SRU is needed. [Test Case] * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates * Run the autopktest in a WSL environment where the user name contains space. * Verify the other individual bugs fixed by the SRU. [Regression Potential] * There is a issue on #1877016 which is already addressed in the next release, but I hope to SRU the current packages in order to prevent future issues when SRUing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+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 1875092] Re: support v5.4 syscalls
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: libseccomp (Ubuntu Eoan) 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/1875092 Title: support v5.4 syscalls Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: New Status in libseccomp source package in Bionic: New Status in libseccomp source package in Eoan: Won't Fix Bug description: [Impact] * update libssecomp syscalls, for example current seccomp on xenial and up, cannot correctly filter calls for focal armhf chroots on v5.4 kernels, due to new syscalls usage. [Test Case] * Boot v5.4 kernel * Use seccomp to try to resolve new syscall numbers * Rebuild snapd snap against bileto ppa with this change * Test that this rebuild snapd snap, can correctly launch confined python armhf interpreter on arm64 v5.4 kernel (i.e. uc20 raspi arm64 beta image) [Regression Potential] * The issue only impacts when one is running on a newer / hwe kernel, and tries to seccomp filter newer binaries that use new syscalls. No changes are made to any existing syscalls or apis. [Other Info] * Bileto PPA with this change is being prepared with this change. xenial: https://bileto.ubuntu.com/#/ticket/4041 bionic: https://bileto.ubuntu.com/#/ticket/4040 eoan: https://bileto.ubuntu.com/#/ticket/4039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1875092/+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 1885248] Re: Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: intel-microcode (Ubuntu Eoan) 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/1885248 Title: Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3 Status in intel-microcode package in Ubuntu: New Status in intel-microcode source package in Xenial: New Status in intel-microcode source package in Bionic: New Status in intel-microcode source package in Eoan: Won't Fix Status in intel-microcode source package in Focal: New Status in intel-microcode source package in Groovy: New Bug description: As a result of https://bugs.launchpad.net/ubuntu/+source/intel- microcode/+bug/1882890 the microcode for 06-4e-03 was reverted from the most recent intel-microcode release to the previous one - Intel has subsequently released a new upstream release https://github.com/intel/Intel-Linux-Processor-Microcode-Data- Files/releases/tag/microcode-20200616 which includes this revert *as well as a revert for the 06-5e-03/0x000506e3 microcode too*. This should also be updated in Ubuntu to ensure we do not suffer any unexpected regressions on these platforms too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1885248/+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 1582811] Re: update-grub produces broken grub.cfg with ZFS mirror volume
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: grub2 (Ubuntu Eoan) Status: Confirmed => 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/1582811 Title: update-grub produces broken grub.cfg with ZFS mirror volume Status in grub2 package in Ubuntu: Confirmed Status in grub2 source package in Xenial: Confirmed Status in grub2 source package in Bionic: Confirmed Status in grub2 source package in Disco: Won't Fix Status in grub2 source package in Eoan: Won't Fix Status in grub2 source package in Focal: Confirmed Bug description: When running update-grub on Xenial with an mirrored ZFS root, broken grub.cfg files are consistently produced due to the root= line being formatted with block devices and a newline inserted. Specifically I get a line like so: linux /ROOT/mint-13@/boot/vmlinuz-4.6.0-040600-generic root=/dev/sdj1 /dev/sdi3 ro nomdmonddf nomdmonisw The newline is what's included. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1582811/+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 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: makedumpfile (Ubuntu Eoan)
Status: Confirmed => 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/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Eoan:
Won't Fix
Status in makedumpfile source package in Focal:
Confirmed
Status in makedumpfile source package in Groovy:
Confirmed
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1770093] Re: Ubiquity crashes with mount points that are FAT16/32
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: partman-basicfilesystems (Ubuntu Eoan) Status: In Progress => 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/1770093 Title: Ubiquity crashes with mount points that are FAT16/32 Status in partman-basicfilesystems package in Ubuntu: In Progress Status in partman-basicfilesystems source package in Xenial: In Progress Status in partman-basicfilesystems source package in Bionic: In Progress Status in partman-basicfilesystems source package in Eoan: Won't Fix Status in partman-basicfilesystems source package in Focal: In Progress Bug description: [impact] when installing on pi with ubiquity, the /boot/firmware partition gets mounted with extra parameters that causes ubiquity to crash. [test case] see original description. [regression potential] this removes the additional mount params from (only) the /boot/firmware mount, so any regression would likely involve problems with that partition. Also since this patches the installation path, regressions may occur during installation. [scope] Debian does not include the extra mount parameters, so Debian does not need patching. This package has been unchanged since bionic. The code needing patching is unchanged between xenial and bionic. This needs patching in all releases (Xenial, Bionic, Eoan, Focal). [original description] Hi, I've used ubiquity as an installer for the Raspberry Pi 2/3. One of the quirks of the Pi is its need for a FAT formatted boot partition. The Pi packages (flash-kernel etc) expect this to be mounted at /boot/firmware. However if I give ubiquity this mount point then it soon crashes. I believe the problem is to do with the mount options that are automatically given to fat partitions. I've solved this by applying a patch to the partman-basicfilesystems package. Please see attached. I'm not sure whether this is the correct fix, or a more generic fix should be applied to ubiquity and FAT partitions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1770093/+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 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: apt-mirror (Ubuntu Eoan) Status: Triaged => 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/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files Status in apt-mirror package in Ubuntu: Triaged Status in apt-mirror source package in Xenial: Confirmed Status in apt-mirror source package in Bionic: Triaged Status in apt-mirror source package in Eoan: Won't Fix Status in apt-mirror source package in Focal: Triaged Status in apt-mirror source package in Groovy: Triaged Bug description: [Impact] * since ubuntu disco, main repositories contains 'cnf' directory with 'Commands*' files. those files are compressed with xy, whereas apt- mirror 0.5.1 doesn't contain the patch which enable download of .xz compressed files * Without this update, users are not able to mirror newer releases of Ubuntu. [Test Case] * On any release of Ubuntu install apt-mirror and add this line to /etc/apt/mirror.list: deb http://archive.ubuntu.com/ubuntu eoan-updates main restricted universe multiverse * sync the mirror using `apt-mirror` * Attempt to run `apt update` against the mirror. The result will be similar to: ... Err:7 http://10.3.0.41/ubuntu eoan-updates/main amd64 c-n-f Metadata 404 Not Found [IP: 10.3.0.41 80] Ign:14 http://10.3.0.41/ubuntu eoan-updates/multiverse amd64 c-n-f Metadata Ign:15 http://10.3.0.41/ubuntu eoan-updates/universe amd64 c-n-f Metadata Ign:16 http://10.3.0.41/ubuntu eoan-updates/restricted amd64 c-n-f Metadata Reading package lists... Done E: Failed to fetch http://10.3.0.41/ubuntu/dists/eoan-updates/main/cnf/Commands-amd64 404 Not Found [IP: 10.3.0.41 80] E: Some index files failed to download. They have been ignored, or old ones used instead. ... * Updating the apt-mirror package from ppa:slashd/test and then re- running the `apt-mirror` command will then allow a successful `apt update`. [Regression Potential] * The regression potential is low since the package doesn't currently work properly anyway. * It's a patchset from a fork repo, if apt-mirror upstream becomes alive again in the future, it won't necessary mean that the fork will be commited/merged upstream, and Ubuntu package might differ from original upstream until next version bump. [Other informations] Upstream bug: https://github.com/apt-mirror/apt-mirror/issues/118 Not much update has been made since Upstream become inactive as noted from the output of rmadison: Since Bionic, it is a simple copy from release to active devel release and so on directly from debian, no patching whatsoever and nothing new to pull from Debian as well. Ubuntu apt-mirror | 0.5.1-1ubuntu1 | xenial/universe | source, all apt-mirror | 0.5.4-1 | bionic/universe | source, all apt-mirror | 0.5.4-1 | disco/universe | source, all apt-mirror | 0.5.4-1 | eoan/universe| source, all apt-mirror | 0.5.4-1 | focal/universe | source, all apt-mirror | 0.5.4-1 | groovy/universe | source, all Debian apt-mirror 0.5.4-1 is found in sid/unstable --- The required patchset is from a fork of upstream apt-mirror josbraden /apt-mirror (https://github.com/josbraden/apt-mirror) Note that upstream apt-mirror is not active anymore, and is looking for a new maintainer as published in their github page: https://github.com/apt-mirror/apt-mirror That's why we have to rely on the fork atm. The required patchset are (tested by Chris in the form of a test pkg: 0001-Copy-DEP-11-functions-for-editing.patch 0001-Replace-DEP-11-with-cnf-in-DEP-11-code-copy.patch 0001-Fix-Regex.patch 0001-Improve-regex-for-cnf-file-matching.patch 0001-Remove-dev-note.patch 0001-Fix-missing-parenthesis.patch I also talked with sil2100 (SRU verification team member) about the feasibilty of this SRU (from a fork repo): " Yeah, I'd say fixes from forked repositories in this case make sense Since there's no longer any 'one authority' for it. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+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 1816743] Re: Add systemd's kdump service command-line regardless if user provides or not KDUMP_CMDLINE_APPEND
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Eoan) Status: Confirmed => 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/1816743 Title: Add systemd's kdump service command-line regardless if user provides or not KDUMP_CMDLINE_APPEND Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Since Xenial release, Ubuntu relies on systemd as its init system - there's a kdump service to prevent some other services to unnecessarily start in kdump environment. Problem: if we add something to KDUMP_CMDLINE_APPEND, the entry for kdump service, "systemd.unit=kdump-tools.service" is removed from the command-line. The user manually needs to add that, and this seems highly prone to error. We propose here to decouple the "systemd.unit=kdump-tools.service" parameter from KDUMP_CMDLINE_APPEND, so if user wants really to remove this option, they should used KDUMP_CMDLINE instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1816743/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-oracle (Ubuntu Eoan) Status: Triaged => 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Triaged Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Triaged Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-4.15 source package in Eoan: Invalid Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1848828] Re: report packages from security pocket
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: landscape-client (Ubuntu Eoan) Status: In Progress => 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/1848828 Title: report packages from security pocket Status in landscape-client package in Ubuntu: In Progress Status in landscape-client source package in Xenial: In Progress Status in landscape-client source package in Bionic: In Progress Status in landscape-client source package in Disco: Won't Fix Status in landscape-client source package in Eoan: Won't Fix Status in landscape-client source package in Focal: In Progress Bug description: [Impact] I report this bug to add the necessary bit into lds-client for all affected/supported releases. [Test Case] * One must use Landscape server on-prem (version >=19.01) or hosted which already contain the necessary server side change. * Install landscape-client. * Successfully register a client against Landscape server. * Security updates will only rely on USN notices and could possibly ignore other packages found in -security pocket even if they are there simply by the fact that there was no USN notice specific for them. (e.g. systemd has an USN, systemd get updated but its derived systemd binary packages aren't updated) [Regression Potential] * The patch flags potential security updates by matching the pocket name. The server then does additional package selection from that info. If the pocket matching were to break, security updates would continue as it was previously. * False positive matching could be possible, assuming one builds a mirror which mimics security pockets and contains normal updates. In that case, landscape could mistakenly update as if they were security updates. * Landscape may apply security updates without USN data, if the update comes from a security pocket. Since this matches the behaviour of unattended-upgrades and MOTD info, this may be closer to what users expect, even though this is a change of behaviour. [Other Info] * Upstream details: https://github.com/CanonicalLtd/landscape-client/commit/93a3b47965da199785e9b3d226cb61f721e54196 https://github.com/CanonicalLtd/landscape-client/pull/57 https://github.com/CanonicalLtd/landscape-client/pull/70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1848828/+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 1842562] Re: AWS: Add udev rule to set Instance Store device IO timeouts
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: cloud-init (Ubuntu Eoan)
Status: In Progress => 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/1842562
Title:
AWS: Add udev rule to set Instance Store device IO timeouts
Status in cloud-init package in Ubuntu:
In Progress
Status in cloud-init source package in Xenial:
In Progress
Status in cloud-init source package in Bionic:
In Progress
Status in cloud-init source package in Disco:
Won't Fix
Status in cloud-init source package in Eoan:
Won't Fix
Bug description:
[Impact]
AWS wish to implement per-device IO timeouts in their cloud, since
currently NVMe devices only support a single global timeout, and this
doesn't play well with EBS volumes, which have error recovery
capabilities built into the back end, and require large timeouts, and
Instance Store / ephemeral volumes, which are to be treated as local
disks, which require short timeouts.
AWS have proposed a solution which is to backport the below two
patches to the Ubuntu kernels:
commit 65cd1d13b880920054d6c750679baa80b7f9c072
Author: Weiping Zhang
Date: Thu Nov 29 00:04:39 2018 +0800
subject: block: add io timeout to sysfs
commit 4d25339e32a1b6e1f490bb78b1e5b0fa9eb3e073
Author: Weiping Zhang
Date: Tue Apr 2 21:14:30 2019 +0800
subject: block: don't show io_timeout if driver has no timeout handler
This enables a sysfs entry in /sys/block/nvmeXnX/queue/io_timeout
which gets and sets the io_timeout per device in milliseconds.
Kernel commits are being tracked in LP #1841461
EBS volumes will use the default timeout as set on the kernel command
line of 4294966296, and Instance Store volumes will need to use a
default timeout of 3.
AWS have suggested that we deploy the below udev rule to automatically
set the io_timeout of all Instance Store volumes to 3:
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
This bug is to add the above udev rule to cloud-init.
[Test Case]
This requires an AWS instance that has Instance Store volumes
configured, and I suggest using c5d.large instances.
I have built a test kernel for bionic linux-aws, version
4.15.0-1043.45+hf240347v20190828b2 which is available from here:
https://launchpad.net/~mruffell/+archive/ubuntu/sf240347-kernel
Install the kernel with the below:
1) sudo add-apt-repository ppa:mruffell/sf240347-kernel
2) sudo apt-get update
Modify grub to boot it, this kernel is 1043, and current is 1044, so
it will likely be "1>2" in grub config:
3) sudo vim /etc/default/grub
Change GRUB_DEFAULT=0 to GRUB_DEFAULT="1>2"
4) sudo update-grub
5) reboot
Once system is up, check kernel version:
6) uname -rv
4.15.0-1043-aws #45+hf240347v20190828b2-Ubuntu SMP Wed Aug 28 06:08:21 UTC
2019
Verify that we have two nvme disks, one EBS and one Instance Store:
7) lsblk
Should have two disks, normally nvme0 and nvme1.
See what device is what:
8) sudo udevadm info --attribute-walk /dev/nvme0
For me, ATTR{model} is "Amazon Elastic Block Store"
9) sudo udevadm info --attribute-walk /dev/nvme1
For me, ATTR{model} is "Amazon EC2 NVMe Instance Storage"
Look at the two timeouts (Note no udev rule yet):
10) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
4294966296
Now we deploy the udev rule:
Place the following line in /lib/udev/rules.d/66-aws-io-timeout.rules
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
Now trigger udev rules:
11) sudo udevadm trigger
Look at the timeouts now:
12) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
3
[Regression Potential]
Regression potential is low since we are adding a udev rule which
applies only to AWS instances, and only for instances which support
Instance Store devices.
The only thing being modified is the device timeout and the udev rule
is robust to device reordering as it goes by model attr information.
When the udev rule is used with unpatched kernels, nothing happens
since the sysfs entry does not exist, and no errors or the like are
reported.
[Other Info]
cloud-init appears to carry azure specific udev rules, which makes me think
that cloud-init is the right place for this requested udev rule to live.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1842562/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
[Group.of.nepali.translators] [Bug 1851663] Re: (In)consistent autopkgtest failures on ppc64el/s390x
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Eoan) Status: Confirmed => 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/1851663 Title: (In)consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+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 1861243] Re: Revert temporary md/raid0 layout patch
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Triaged => 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/1861243 Title: Revert temporary md/raid0 layout patch Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: A "temporary" patch was applied to Xenial, Bionic, Disco and Eoan as part of the fix for: https://bugs.launchpad.net/bugs/1850540: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/commit/?id=faf36efcc6d6bf50c9b5a2a6d7f0efdae296e8a6 "UBUNTU: SAUCE: md/raid0: Use kernel specific layout" (this uses by default the layout for multi-zone md RAID0 arrays that the kernel was using before / instead of failing to assemble those and require the user to make a choice). Once the rollout of a fixed user-space and maybe some grace period we should revert this to be back behaving like upstream does. This bug is for tracking the reversion of the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861243/+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 1873074] Re: kernel panic hit by kube-proxy iptables-save/restore caused by aufs
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => 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/1873074 Title: kernel panic hit by kube-proxy iptables-save/restore caused by aufs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Systems with aufs mounts are vulnerable to a kernel BUG(), which can turn into a panic/crash if panic_on_oops is set. * It is exploitable by unprivileged local users; and also remote access operations (e.g., web server) potentially. * This issue has also manifested in Kubernetes deployments with a kernel panic in iptables-save or iptables-restore after a few weeks of uptime, without user interaction. * Usually all Kubernetes worker nodes hit the issue around the same time. [Fix] * The issue is fixed with 2 patches in aufs4-linux.git: - 515a586eeef3 aufs: do not call i_readcount_inc() - f10aea57d39d aufs: bugfix, IMA i_readcount * The first addresses the issue, and the second addresses a regression in the aufs feature to change RW branches to RO. * The kernel v5.3 aufs patches had an equivalent fix to the second patch, which is present in the Focal aufs patchset (and on ubuntu-unstable/master & /master-5.8 on 20200629) - 1d26f910c53f aufs: for v5.3-rc1, maintain i_readcount (in aufs5-linux.git) [Test Case] * Repeatedly open/close the same file in read-only mode in aufs (UINT_MAX times, to overflow a signed int back to 0.) * Alternatively, monitor the underlying filesystems's file inode.i_readcount over several open/close system calls. (should not monotonically increase; rather, return to 0.) [Regression Potential] * This changes the core path that aufs opens files, so there is a risk of regression; however, the fix changes aufs for how other filesystems work, so this generally is OK to do. In any case, most regressions would manifest in open() or close() (where the VFS handles/checks inode.i_readcount.) * The aufs maintainer has access to an internal test-suite used to validate aufs changes, used to identify the first regression (in the branch RW/RO mode change), and then to validate/publish the patches upstream; should be good now. * This has also been tested with 'stress-ng --class filesystem' and with 'xfstests -overlay' (patch to use aufs vs overlayfs) on Xenial/Bionic/Focal (-proposed vs. -proposed + patches). No regressions observed in stress-ng/xfstests log or dmesg. [Other Info] * Applied on Unstable (branches master and master-5.8) * Not required on Groovy (still 5.4; should sync from Unstable) * Required on LTS releases: Bionic and Focal and Xenial. * Required on other releases: Disco and Eoan (for custom kernels) [Original Bug Description] Problem Report: -- An user reported several nodes in their Kubernetes clusters hit a kernel panic at about the same time, and periodically (usually 35 days of uptime, and in same order nodes booted.) The kernel panics message/stack trace are consistent across nodes, in __fput() by iptables-save/restore from kube-proxy. Example: """ [3016161.866702] kernel BUG at .../include/linux/fs.h:2583! [3016161.866704] invalid opcode: [#1] SMP ... [3016161.866780] CPU: 40 PID: 33068 Comm: iptables-restor Tainted: P OE 4.4.0-133-generic #159-Ubuntu ... [3016161.866786] RIP: 0010:[...] [...] __fput+0x223/0x230 ... [3016161.866818] Call Trace: [3016161.866823] [...] fput+0xe/0x10 [3016161.866827] [...] task_work_run+0x86/0xb0 [3016161.866831] [...] exit_to_usermode_loop+0xc2/0xd0 [3016161.866833] [...] syscall_return_slowpath+0x4e/0x60 [3016161.866839] [...] int_ret_from_sys_call+0x25/0x9f """ (uptime: 3016161 seconds / (24*60*60) = 34.90 days) They have provided a crashdump (privately available) used for analysis later in this bug report. Note: the root cause turns out to be independent of K8s, as explained in the Root Cause section. Related Report: -- This behavior matches this public bug of another user: https://github.com/kubernetes/kubernetes/issues/70229 """ I have several machines happen kernel panic，and these machine have same dump trace like below: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-104-generic ... PANIC: "kernel BUG at .../include/linux/fs.h:2582!"
[Group.of.nepali.translators] [Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: mysql-8.0 (Ubuntu Eoan)
Status: Triaged => 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/1877442
Title:
Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1
Status in mysql-5.7 package in Ubuntu:
Triaged
Status in mysql-8.0 package in Ubuntu:
Triaged
Status in mysql-5.7 source package in Xenial:
Triaged
Status in mysql-8.0 source package in Xenial:
Invalid
Status in mysql-5.7 source package in Bionic:
Triaged
Status in mysql-8.0 source package in Bionic:
Invalid
Status in mysql-5.7 source package in Eoan:
Invalid
Status in mysql-8.0 source package in Eoan:
Won't Fix
Status in mysql-5.7 source package in Focal:
Invalid
Status in mysql-8.0 source package in Focal:
Triaged
Bug description:
[Impact]
This is a regression in MySQL 5.7.30 (does not affect 8.0 which is in focal
and development release, nor 5.7.29). The CONCAT function has inconsistent
behavior depending on whether or not the result is assigned to a variable,
which is leading to a crash in slurmdbd.
Since it's limited to 5.7.30, the bug only affects stable releases
Bionic and Xenial.
[Test Case]
- Start up MySQL Server 5.7.30
- Connect to it with the mysql cli (with default install of the server, "sudo
mysql" will connect to the MySQL root user)
- Run the following two queries:
* SELECT CONCAT('');
* SET @var = ""; SELECT @var := CONCAT('');
They should give the same output, but the second one returns NULL instead of
an empty string when using 5.7.30.
[Regression Potential]
The patch changes fairly low-level code, which can always carry some risk.
[Other info]
This bug is fixed in the next upstream release of MySQL (5.7.31), so the
patch would only be needed until that is picked.
--- ORIGINAL DESCRIPTION ---
Hi,
Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
segfaulting.
Upon inspection, the slurmdbd crash is caused by a change of behaviour
of the SQL CONCAT function. The new behaviour seems wrong.
Calling
SELECT CONCAT('');
will result in an empty string as expected however if the result is assigned
to a variable with:
SET @var = ""; SELECT @var := CONCAT('');
the variable will be NULL instead of an empty string.
It seems that when the output of CONCAT is assigned to a variable; if
CONCAT should have returned an empty string, it will set the variable
to NULL instead.
SLURM itself crashes because it uses a stored procedure which relies
on the output of CONCAT to be an empty string rather than a NULL
variable and tries to dereference the pointer.
I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I
tested on 5.7.21-1ubuntu1. On 5.7.21, the variable was correctly set
to an empty string. I have also tried on 20.04 and the behaviour is
correct as well. So the problem seems to be present only in the
version 5.7.30-0ubuntu0.18.04.1.
I think that the behaviour was introduced in the 5.7 branch by this commit:
https://github.com/mysql/mysql-server/commit/addb2aab601d98e685eccae545f79d120561ad9b
but I am not entirely sure.
This bug is a bit annoying because it makes SLURM with accounting
enabled completely unusable. However downgrading MySQL to
5.7.29-0ubuntu0.18.04.1 temporarily fixed the problem.
I have attached a log file with examples to reproduce the bug.
Thank you very much.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => 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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Won't Fix
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of bcache who manually specified a block size
greater than the page size when creating the device
with 'make-bcache' started to hit a kernel BUG/oops
after kernel upgrades. (This is not widely used.)
* The issue has been exposed with commit ad6bf88a6c19
("block: fix an integer overflow in logical block size")
because it increased the range of values accepted as
logical block size, which used to overflow to zero,
and thus receive a default of 512 via block layer.
* The issue existed previously, but with fewer values
exposed (e.g. 8k, 16k, 32k); the regression reports
happened with larger values (512k) for RAID stripes.
[Fix]
* The upstream commit dcacbc1242c7 ("bcache: check and
adjust logical block size for backing devices") checks
the block size and adjusts it if needed, to the value
of the underlying device's logical block size.
* It is merged as of v5.8-rcN, and sent to v5.7 stable.
[Test Case]
* Run make-bcache with block size greater than page size.
$ sudo make-bcache --bdev $DEV --block 8k
* Expected results: bcache device registered; no BUG/oops.
* Details steps on comment #43.
[Regression Potential]
* Restricted to users who specify a bcache block size
greater than page size.
* Regressions could theoretically manifest on bcache
device probe/register, if the underlying device's
logical block size for whatever triggers issues not
seen previously with the overflow/default 512 bytes.
[Other Info]
* Unstable has the patch on both master/master-5.7.
* Groovy should get it on rebase.
[Original Bug Description]
After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does
not boot any longer. It always crashes during boot with a kernel panic.
I suspect that this crash might be related to Bcache because this is
the only one of our systems where we use Bcache and the kernel panic
appears right after Bcache initialization.
I already checked that this bug still exists in the 4.15.0-92.93
kernel from proposed.
Unfortunately, I cannot do a bisect because this is a critical
production system and we do not have any other system with a similar
configuration.
I attached a screenshot with the trace of the kernel panic.
The last message that appears before the kernel panic (or rather the
last one that I can see - there is a rather long pause between that
message and the panic and I cannot scroll up far enough to ensure that
there are no other messages in between) is:
bcache: register_bcache() error /dev/dm-0: device already registered
When booting with kernel 4.15.0-88 that does not have this problem,
the next message is
bcache: register_bcache() error /dev/dm-12: device already registered
(emitting change event)
After that the next message is:
Begin: Loading essential drivers ... done
This message also appears after the kernel panic, but the boot process
stalls and the system can only be recovered by doing a hardware reset.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-88-generic 4.15.0-88.88
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 17 21:08 seq
crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 18 12:55:18 2020
HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
InstallationDate: Installed on 2013-07-02 (2450 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release
amd64 (20130214)
MachineType: HP ProLiant DL160 G6
PciMultimedia:
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic
[Group.of.nepali.translators] [Bug 1881982] Re: DoS vulnerability: cause resource exhaustion
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: whoopsie (Ubuntu Eoan) Status: Confirmed => 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/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Bionic: Fix Released Status in whoopsie source package in Eoan: Won't Fix Status in whoopsie source package in Focal: Fix Released Status in whoopsie source package in Groovy: Fix Released Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => 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/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_sock()
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Won't Fix
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of the Linux kernel's crypto userspace API
reported BUG() / kernel NULL pointer dereference
errors after kernel upgrades.
* The stack trace signature is an accept() syscall
going through af_alg_accept() and hitting errors
usually in one of:
- apparmor_sk_clone_security()
- apparmor_sock_graft()
- release_sock()
[Fix]
* This is a regression introduced by upstream commit
37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
in sk_destruct") which made its way through stable.
* The offending patch allows the critical regions
of af_alg_accept() and af_alg_release_parent() to
run concurrently; now with the "right" events on 2
CPUs it might drop the non-atomic reference counter
of the alg_sock then the sock, thus release a sock
that is still in use.
* The fix is upstream commit 34c86f4c4a7b ("crypto:
af_alg - fix use-after-free in af_alg_accept() due
to bh_lock_sock()") [1]. It changes alg_sock's ref
counter to atomic, which addresses the root cause.
[Test Case]
* There is a synthetic test case available, which
uses a kprobes kernel module to synchronize the
concurrent CPUs on the instructions responsible
for the problem; and a userspace part to run it.
* The organic reproducer is the Varnish Cache Plus
software with the Crypto vmod (which uses kernel
crypto userspace API) under long, very high load.
* The patch has been verified on both reproducers
with the 4.15 and 5.7 kernels.
* More tests performed with 'stress-ng --af-alg'
with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
(all on same version of stress-ng, V0.11.14)
No regressions observed from original kernel.
(the af-alg stressor can exercise almost all
kernel crypto modules shipped with the kernel;
so it checks more paths/crypto alg interfaces.)
[Regression Potential]
* The fix patch does a fundamental change in how
alg_sock reference counters work, plus another
change to the 'nokey' counting. This of course
*has* a risk of regression.
* Regressions theoretically could manifest as use
after free errors (in case of undercounting) in
the af_alg functions or silent memory leaks (in
case of overcounting), but also other behaviors
since reference counting is key to many things.
* FWIW, this patch has been written by the crypto
subsystem maintainer, who certainly knows a lot
of the normal and corner cases, thus giving the
patch more credit.
* Testing with the organic reproducer ran as long
as 5 days, without issues, so it does look good.
[Other Info]
* Not sending for Groovy (should get via Unstable).
* [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
[Stack Trace Examples]
Examples:
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:apparmor_sk_clone_security+0x26/0x70
...
Call Trace:
security_sk_clone+0x33/0x50
af_alg_accept+0x81/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
SyS_accept+0x10/0x20
do_syscall_64+0x73/0x130
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
general protection fault: [#1] SMP PTI
...
RIP: 0010:__release_sock+0x54/0xe0
...
Call Trace:
release_sock+0x30/0xa0
af_alg_accept+0x122/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
SyS_accept+0x10/0x20
do_syscall_64+0x73/0x130
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884766/+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 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
eoan has reached end of life, so this bug will not be fixed for that release ** Changed in: python2.7 (Ubuntu Eoan) Status: Triaged => 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/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Status in python3.5 package in Ubuntu: Invalid Status in python2.7 source package in Xenial: Fix Released Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Bionic: Fix Released Status in python3.5 source package in Bionic: Invalid Status in python2.7 source package in Cosmic: Won't Fix Status in python3.5 source package in Cosmic: Invalid Status in python2.7 source package in Disco: Fix Released Status in python3.5 source package in Disco: Invalid Status in python2.7 source package in Eoan: Won't Fix Status in python3.5 source package in Eoan: Invalid Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+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 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
This bug was fixed in the package openssh - 1:8.0p1-6ubuntu0.1 --- openssh (1:8.0p1-6ubuntu0.1) eoan; urgency=medium * Apply upstream patch to stop using 2020 as a future date in regress tests. LP: #1859013 -- Dimitri John Ledkov Thu, 09 Jan 2020 23:53:27 + ** Changed in: openssh (Ubuntu Eoan) 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/1859013 Title: openssh tests use "not valid yet" certificate from 2020, which is now valid Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Precise: New Status in openssh source package in Trusty: New Status in openssh source package in Xenial: Fix Released Status in openssh source package in Bionic: Fix Committed Status in openssh source package in Disco: Won't Fix Status in openssh source package in Eoan: Fix Released Status in openssh source package in Focal: Fix Released Bug description: [Impact] * regression testsuite uses 1st of January 2020 as the date in the future, however that is now in the past making autpkgtests fail. [Test Case] * Autopkgtest must pass [Regression Potential] * Testsuite assertion update only [Other Info] This is a staged update to be rolled up with any other openssh update in the future. fixed in debian https://tracker.debian.org/news/1092767/accepted- openssh-181p1-4-source-into-unstable/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1890790] Re: Build Failure with --enable-ssl-crtd flag
I am attempting to rebuild the package with no modification apart from a change to the configuration options in debian/rules before recompiling. apt source -y squid cd squid* && sed -i 's/--with-large-files/--with-large-files --with-openssl --enable-ssl-crtd/g' debian/rules debuild -b -uc -us -j$(nproc) This used to work until the squid3_3.5.12-1ubuntu7.12 update without any modifications to the method of rebuilding. This is occurring on two 16.04 machines, one of which was a fresh install. Thanks ** Changed in: squid3 (Ubuntu) Status: Invalid => New ** Changed in: squid3 (Ubuntu Xenial) Status: Invalid => 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/1890790 Title: Build Failure with --enable-ssl-crtd flag Status in squid3 package in Ubuntu: New Status in squid3 source package in Xenial: New Bug description: I have a script that grabs the latest package source for squid3 and builds, adding the --enable-ssl-crtd and --with-openssl flags. After the last package update "squid3_3.5.12-1ubuntu7.12.debian.tar.xz" this errors out during compilation. I have narrowed it down to the --enable-ssl-crtd flag. The error is as follows: ssl/certificate_db.h:56:0: error: "Here" redefined [-Werror] #define Here __FILE__, __LINE__ ^ In file included from ../src/base/TextException.h:15:0, from ../src/SBufExceptions.h:12, from ../src/SBuf.h:14, from ../src/http/MethodType.h:12, from ../src/HttpRequestMethod.h:12, from ../src/AccessLogEntry.h:18, from acl/FilledChecklist.h:12, from client_side.cc:61: ../src/base/Here.h:15:0: note: this is the location of the previous definition #define Here() SourceLocation(__FUNCTION__, __FILE__, __LINE__) ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1890790/+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 1890662] Re: xenial/linux-kvm: 4.4.0-1079.86 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-kvm meta: linux-meta-kvm - phase: Promote to Proposed - phase-changed: Tuesday, 18. August 2020 08:53 UTC + phase: Testing + phase-changed: Tuesday, 18. August 2020 10:44 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for - mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1079.86 meta: 4.4.0.1079.77 -- 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/1890662 Title: xenial/linux-kvm: 4.4.0-1079.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 18. August 2020 10:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs versions: main: 4.4.0-1079.86 meta: 4.4.0.1079.77 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1890662/+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 1890667] Re: xenial/linux-fips: 4.4.0-1045.50 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Building in Signing - phase-changed: Tuesday, 18. August 2020 06:28 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 18. August 2020 08:17 UTC reason: - build-packages-signing: Ongoing -- building in Signing - signed:depwait - promote-to-proposed: Stalled -- packages copying to Signing + promote-signing-to-proposed: Pending -- ready for review variant: debs versions: main: 4.4.0-1045.50 meta: 4.4.0.1045.47 signed: 4.4.0-1045.50 -- 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/1890667 Title: xenial/linux-fips: 4.4.0-1045.50 -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: 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-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891057 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Tuesday, 18. August 2020 08:17 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs versions: main: 4.4.0-1045.50 meta: 4.4.0.1045.47 signed: 4.4.0-1045.50 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1890667/+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 1890700] Re: xenial/linux-oracle: 4.15.0-1051.55~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1890701 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Packaging - phase-changed: Friday, 14. August 2020 20:06 UTC + phase: Building in ppa + phase-changed: Tuesday, 18. August 2020 08:01 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded - prepare-package-signed: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building variant: debs + versions: + main: 4.15.0-1051.55~16.04.1 + meta: 4.15.0.1051.42 + signed: 4.15.0-1051.55~16.04.1 -- 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/1890700 Title: xenial/linux-oracle: 4.15.0-1051.55~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1890701 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Building in ppa phase-changed: Tuesday, 18. August 2020 08:01 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building variant: debs versions: main: 4.15.0-1051.55~16.04.1 meta: 4.15.0.1051.42 signed: 4.15.0-1051.55~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1890700/+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 1890704] Re: xenial/linux-hwe: 4.15.0-114.115~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891052 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Promote to Proposed - phase-changed: Tuesday, 18. August 2020 06:27 UTC + phase: Testing + phase-changed: Tuesday, 18. August 2020 07:57 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for - mirror sync + automated-testing: Stalled -- testing FAILED + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1890703 variant: debs versions: main: 4.15.0-114.115~16.04.1 meta: 4.15.0.114.115 signed: 4.15.0-114.115~16.04.1 -- 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/1890704 Title: xenial/linux-hwe: 4.15.0-114.115~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1891052 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Tuesday, 18. August 2020 07:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1890703 variant: debs versions: main: 4.15.0-114.115~16.04.1 meta: 4.15.0.114.115 signed: 4.15.0-114.115~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1890704/+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
