[Group.of.nepali.translators] [Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Testing phase-changed: Tuesday, 23. July 2019 22:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress variant: debs -- 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/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Testing phase-changed: Tuesday, 23. July 2019 22:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+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 1837605] Re: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Wednesday, 31. July 2019 22:26 UTC + phase: Signoff + phase-changed: Wednesday, 31. July 2019 22:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs -- 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/1837605 Title: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed 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 derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 31. July 2019 22:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837605/+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 1837605] Re: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -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 => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Wednesday, 31. July 2019 15:55 UTC + phase: Testing + phase-changed: Wednesday, 31. July 2019 22:26 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs -- 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/1837605 Title: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed 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 derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Wednesday, 31. July 2019 22:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837605/+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 1775636] Re: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA
Only xenial affected, adjusting bug tasks ** Also affects: sssd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu Xenial) Status: New => Triaged ** Changed in: sssd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: sssd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775636 Title: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Triaged Bug description: When trying to get the key for a person with also a client cert present in IPA the following error shows: ``` (Thu Jun 7 14:37:11:920526 2018) [/usr/bin/sss_ssh_authorizedkeys] [main] (0x0020): sss_ssh_get_ent() failed (14): Bad address Error looking up public keys ``` What is supposed to happen: return public key for user Version Information: Ubuntu 16.04.2 LTS Updated sssd-common and related tools to latest: libipa-hbac0 libsss- idmap0 python-libipa-hbac python-sss sssd sssd-ad sssd-ad-common sssd- common sssd-ipa sssd-krb5 sssd-krb5-common sssd-ldap sssd-proxy so sssd is now at: ii sssd-common1.13.4-1ubuntu1.10 amd64System Security Services Daemon -- common files This doesn't happen on Centos 7.5 (sssd-common-1.16.0-19.el7.x86_64) nor on ubuntu 14.04 (sssd-common==1.11.8-0ubuntu0.7) IPA server is on CentOS 7.5: ipa-server-4.5.4-10.el7.centos.x86_64 From what I've seen upstream, it might be related to the fairly new handling of x509 certificates with ssh certificates in them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1775636/+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 1837397] Re: Make possible to load Mellanox OFED modules
** Changed in: linux-azure (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Cosmic) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1837397 Title: Make possible to load Mellanox OFED modules Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Cosmic: Invalid Status in linux-azure source package in Disco: Fix Committed Bug description: [Impact] Infiniband and Mellanox modules are currently built-in which makes impossible for users to build and load OFED drivers. [Test Case] Users should be able to build and load OFED drivers without conflicting with the built-in drivers. [Regression Potential] The major regression potential is related to the linux-modules or linux-modules-extra packages. The built-in modules should be build as loadable modules and placed at the linux-modules package, having then in the linux-modules-extra package will cause issues for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837397/+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 1790657] Re: [SRU] amqp-tools server parameter unusable
This bug was fixed in the package librabbitmq - 0.7.1-1ubuntu0.1 --- librabbitmq (0.7.1-1ubuntu0.1) xenial; urgency=medium * d/patches: Add fix-parameter-processing.patch to correct handling of --server, --url, and other options by reorganizing the logic flow. (LP: #1790657) -- Bryce Harrington Mon, 08 Jul 2019 20:19:04 -0700 ** Changed in: librabbitmq (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790657 Title: [SRU] amqp-tools server parameter unusable Status in librabbitmq package in Ubuntu: Fix Released Status in librabbitmq source package in Xenial: Fix Released Status in librabbitmq source package in Bionic: Fix Released Status in librabbitmq source package in Cosmic: Won't Fix Status in librabbitmq source package in Disco: Fix Released Status in librabbitmq source package in Eoan: Fix Released Bug description: [Impact] The --server and -url parameters do not function as documented, due to an upstream coding error that was fixed in release 0.8.1. [Test Case] $ sudo apt-get -y install librabbitmq-dev $ sudo apt-get -y install amqp-tools ### Broken behavior: $ sudo amqp-consume --server=foobar:5672 -q queue cat both --server and --url options specify server host ### Fixed behavior: $ sudo apt-add-repository -y ppa:bryce/librabbitmq-sru-1790657 $ sudo apt-get -y install librabbitmq-dev $ sudo amqp-consume --server=foobar:5672 -q queue cat Specifying the port number with --server is deprecated opening socket to foobar:5672 [Regression Potential] The patch alters C code to change how command line options are processed. Things to watch for, then, would be mishandling of cli options, or compilation errors during package build. The changes do not alter input handling at all, so static testing should give a high degree of confidence of stability. Also, the alterations are focused on tools, so general operation of librabbitmq should not be affected in any way by the changes. [Fix] The upstream patch corrects handling of --server, --url, and other options by reorganizing the logic flow. [Discussion] The issue appears not to be a regression from a recent change, but a problem that has existed for quite a while: librabbitmq | 0.0.1.hg216-1 | precise/universe | source librabbitmq | 0.4.1-1 | trusty | source librabbitmq | 0.7.1-1 | xenial/universe | source librabbitmq | 0.8.0-1build1 | bionic/universe | source librabbitmq | 0.8.0-1build1 | cosmic/universe | source librabbitmq | 0.9.0-0.2 | disco| source librabbitmq | 0.9.0-0.2 | eoan | source The fix should be backported to bionic and probably cosmic. Earlier releases are probably also affected but probably only worth doing if the patch applies cleanly to them. [Original Report] The version of amqp-tools in 18.04.1 LTS (and 14.04 iirc) has a bug which renders parts of the cli unusable: https://github.com/alanxz/rabbitmq-c/issues/364 1) 18.04.1 LTS bionic 2) 0.8.0-1build1 3) `amqp-consume --server=foobar:5672 -q queue cat` should work 4) amqp-consume complains that you cannot use --server and --url together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librabbitmq/+bug/1790657/+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 1835818] Re: snmpd causes autofs mount points to be mounted on service start/restart
** Changed in: net-snmp (Ubuntu Cosmic) 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/1835818 Title: snmpd causes autofs mount points to be mounted on service start/restart Status in net-snmp package in Ubuntu: In Progress Status in net-snmp source package in Xenial: In Progress Status in net-snmp source package in Bionic: In Progress Status in net-snmp source package in Cosmic: Won't Fix Status in net-snmp source package in Disco: In Progress Status in net-snmp source package in Eoan: In Progress Bug description: [Impact] Autofs direct map triggers are visible in /etc/mtab. On boot, when snmpd starts, it iterates over the entries in /etc/mtab and performs statfs() on them. This trigger automount to mount autofs mounts even if the user does not explicitly access them. However this happens only if autofs service is started before snmpd. If snmpd stars first /etc/mtab is not yet populated with autofs mounts and therefore are not mounted. When there a few autofs mount points the impact is insignificant. However when there are thousands of them, this causes unnecessary overhead on operations such as df. This also delays the system shutdown time since everything needs to be unmounted. [Test Case] *** Test Case 1 - During boot: The user that brought this issue to our attention would observe all autofs mounts be mounted at boot, because in their environment autofs would start first. In my environment snmpd starts first so to reproduce I had to add a small delay in snmpd init script. In /etc/init.d/snmp : @@ -36,6 +36,8 @@ cd / case "$1" in start) +# Delay snmp start +sleep 2 log_daemon_msg "Starting SNMP services:" # remove old symlink with previous version if [ -L /var/run/agentx ]; then $cat /etc/auto.master /- /etc/auto.nfs --timeout=30 $cat /etc/auto.nfs /home/test1 -fstype=nfs,hard,intr,nosuid,no-subtree-check,tcp :/srv/export/test1 /home/test2 -fstype=nfs,hard,intr,nosuid,no-subtree-check,tcp :/srv/export/test2 Reboot vm, syslog entries : # Autofs starts Jul 11 11:04:16 xenial-vm3 autofs[1295]: * Starting automount... Jul 11 11:04:16 xenial-vm3 automount[1357]: Starting automounter version 5.1.1, master map /etc/auto.master Jul 11 11:04:16 xenial-vm3 automount[1357]: using kernel protocol version 5.02 # Mount triggers, now visible in mtab Jul 11 11:04:16 xenial-vm3 automount[1357]: mounted direct on /home/test1 with timeout 300, freq 75 seconds Jul 11 11:04:16 xenial-vm3 automount[1357]: mounted direct on /home/test2 with timeout 300, freq 75 seconds Jul 11 11:04:16 xenial-vm3 autofs[1295]:...done. ... # SNMP starts Jul 11 11:04:18 xenial-vm3 snmpd[1294]: * Starting SNMP services: Jul 11 11:04:18 xenial-vm3 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1394 (snmpd) Jul 11 11:04:18 xenial-vm3 systemd[1]: Mounting Arbitrary Executable File Formats File System... Jul 11 11:04:18 xenial-vm3 systemd[1]: Mounted Arbitrary Executable File Formats File System. Jul 11 11:04:18 xenial-vm3 automount[1357]: attempting to mount entry /home/test1 <== Jul 11 11:04:18 xenial-vm3 kernel: [8.880685] FS-Cache: Loaded Jul 11 11:04:18 xenial-vm3 kernel: [8.889318] FS-Cache: Netfs 'nfs' registered for caching Jul 11 11:04:18 xenial-vm3 kernel: [8.902672] NFS: Registering the id_resolver key type Jul 11 11:04:18 xenial-vm3 kernel: [8.902680] Key type id_resolver registered Jul 11 11:04:18 xenial-vm3 kernel: [8.902682] Key type id_legacy registered Jul 11 11:04:18 xenial-vm3 automount[1357]: mounted /home/test1 <== Jul 11 11:04:18 xenial-vm3 automount[1357]: attempting to mount entry /home/test2 <== Jul 11 11:04:18 xenial-vm3 kernel: [9.163011] random: nonblocking pool is initialized Jul 11 11:04:18 xenial-vm3 automount[1357]: mounted /home/test2 <=== *** Test Case 2 - Restart snmpd : To reproduce this case, autofs mounts should not be mounted to begin with. (restart autofs or let it expire) #systemctl restart snmpd.service Syslog entries : Jul 11 11:15:40 xenial-vm3 systemd[1]: Stopping LSB: SNMP agents... Jul 11 11:15:40 xenial-vm3 snmpd[1668]: * Stopping SNMP services: Jul 11 11:15:40 xenial-vm3 snmpd[1434]: Received TERM or STOP signal... shutting down... Jul 11 11:15:40 xenial-vm3 systemd[1]: Stopped LSB: SNMP agents. Jul 11 11:15:40 xenial-vm3 systemd[1]: Starting LSB: SNMP agents... Jul 11 11:15:42 xenial-vm3 snmpd[1677]: * Starting SNMP services: Jul 11 11:15:42 xenial-vm3 automount[1357]: attempting to mount entry /home/test1 <=== Jul 11 11:15:42 xenial-vm3
[Group.of.nepali.translators] [Bug 1837588] Re: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 derivatives: bug 1837587 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Wednesday, 31. July 2019 12:20 UTC + phase: Signoff + phase-changed: Wednesday, 31. July 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs -- 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/1837588 Title: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed 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 derivatives: bug 1837587 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Wednesday, 31. July 2019 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837588/+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 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 derivatives: bug 1837592 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Testing - phase-changed: Tuesday, 30. July 2019 22:35 UTC + phase: Signoff + phase-changed: Wednesday, 31. July 2019 14:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1837592 variant: debs -- 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/1837594 Title: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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 derivatives: bug 1837592 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Wednesday, 31. July 2019 14:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1837592 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+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 1838533] [NEW] Bionic linux 4.15.0-56.62 fails to build with CONFIG_NVM disabled
Public bug reported:
[Impact]
When compiling bionic linux 4.15.0-56.62 with CONFIG_NVM disabled, it
fails with:
make[5]: *** [drivers/nvme/host/core.o] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/multipath.c:15:0:
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h: In function
'nvme_nvm_register_sysfs':
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: error:
'ctrl' undeclared (first use in this function)
if (ctrl->subsys->cmic & (1 << 3))
^
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: note:
each undeclared identifier is reported only once for each function it appears in
[Fix]
The culprit seems to be this patch:
commit 993f70b886c0062fb5ec7c3c556d074bb3380b9d
Author: Christoph Hellwig
Date: Tue Nov 20 16:57:54 2018 +0100
nvme: warn when finding multi-port subsystems without multipathing
enabled
BugLink: https://bugs.launchpad.net/bugs/1837161
[ Upstream commit 14a1336e6fff47dd1028b484d6c802105c58e2ee ]
[...]
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -499,6 +499,9 @@ static inline int nvme_nvm_register(struct nvme_ns *ns,
char *disk_name,
static inline void nvme_nvm_unregister(struct nvme_ns *ns) {};
static inline int nvme_nvm_register_sysfs(struct nvme_ns *ns)
{
+ if (ctrl->subsys->cmic & (1 << 3))
+ dev_warn(ctrl->device,
+"Please enable CONFIG_NVME_MULTIPATH for full support of multi-port
devices.\n");
return 0;
}
which is adding the new lines to a different function than the original
upstream commit:
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -531,6 +531,9 @@ static inline void nvme_mpath_check_last_path(struct
nvme_ns *ns)
static inline int nvme_mpath_init(struct nvme_ctrl *ctrl,
struct nvme_id_ctrl *id)
{
+ if (ctrl->subsys->cmic & (1 << 3))
+ dev_warn(ctrl->device,
+"Please enable CONFIG_NVME_MULTIPATH for full support of multi-port
devices.\n");
return 0;
}
This patch was probably wrongly backported for bug #1837161 from
linux-4.19.y stable and not needed since bionic/linux lacks commit
0d0b660f214d (nvme: add ANA support) which introduced nvme_mpath_init().
The fix is to revert this patch.
[Test Case]
Disabled kernel config CONFIG_NVM and compile the kernel.
[Regression Potential]
Low. The patch was wrongly backported and can be safely reverted.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: Invalid
** Affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Invalid
** Description changed:
[Impact]
When compiling bionic linux 4.15.0-56.62 with CONFIG_NVM disabled, it
fails with:
make[5]: *** [drivers/nvme/host/core.o] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/multipath.c:15:0:
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h: In function
'nvme_nvm_register_sysfs':
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: error:
'ctrl' undeclared (first use in this function)
- if (ctrl->subsys->cmic & (1 << 3))
- ^
+ if (ctrl->subsys->cmic & (1 << 3))
+ ^
/tmp/kernel-kleber-57dc2e6-NQe1/build/drivers/nvme/host/nvme.h:502:6: note:
each undeclared identifier is reported only once for each function it appears in
- [Fix]
+ [Fix]
The culprit seems to be this patch:
commit 993f70b886c0062fb5ec7c3c556d074bb3380b9d
Author: Christoph Hellwig
Date: Tue Nov 20 16:57:54 2018 +0100
- nvme: warn when finding multi-port subsystems without multipathing enabled
-
- BugLink: https://bugs.launchpad.net/bugs/1837161
-
- [ Upstream commit
[Group.of.nepali.translators] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
A fix for this was added for bionic at version 1.10.14-0ubuntu2, but
that was reverted due to regressions, so this is not yet fixed in
bionic-updates
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
New
Status in network-manager source package in Bionic:
In Progress
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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/1795659
Title:
kernel panic using CIFS share in smb2_push_mandatory_locks()
Status in linux package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux-azure source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Won't Fix
Status in linux-azure source package in Cosmic:
Invalid
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Invalid
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
BUG: unable to handle kernel NULL pointer dereference at 0038
IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
PGD 0 P4D 0
RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
Call Trace:
cifs_oplock_break+0x12f/0x3d0 [cifs]
process_one_work+0x14d/0x410
worker_thread+0x4b/0x460
kthread+0x105/0x140
[...]
* Low-level analysis (decodecode script output and the objdump of the
function) revealed that we are crashing in a NULL ptr dereference when
trying to access "cfile->tlink"; below, a snippet of the objdump at
function smb2_push_mandatory_locks():
[...]
mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile
mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks)
lea0x18(%r14),%r12
mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink)
cmp%r12,%rbx
mov0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon]
[...]
* After discussing the issue with CIFS maintainers (Steve French and
Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep
FileInfo handle live during oplock break")
[http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple
reports of this kind of crash.
* The fix was sent to stable kernels and is present in Ubuntu kernels
5.0 and newer. We are requesting the SRU for this patch here in order
to fix the crashes, after reports of successful testing with the patch
(see below section) and since the patch is restricted to the cifs
module scope and accepted on linux stable.
* Alternatively the issue is known to be avoided when oplocks are
disabled using "cifs.enable_oplocks=N" module parameter.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we
have a user report of test validation using LISA
(https://github.com/LIS/LISAv2).
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers (in fact
they suggested its inclusion in Ubuntu) and by the aforementioned
tests; also, the scope is restricted to cifs only so the likelihood of
regressions is considered low.
* Due to the nature of the code modification (add a new reference of a
file handler and manipulate it in different places), I consider that
if we have a regression it'll manifest as deadlock/blocked tasks, not
something more serious like crashes or data corruption.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+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 1837588] Re: xenial/linux-aws: 4.4.0-1089.100 -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 => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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 derivatives: bug 1837587 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Wednesday, 31. July 2019 09:30 UTC + phase: Testing + phase-changed: Wednesday, 31. July 2019 12:20 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs -- 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/1837588 Title: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed 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 derivatives: bug 1837587 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 31. July 2019 12:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837588/+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 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+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 1830242] Re: [linux-azure] Commits Requested in 16.04 for the Azure Kernel
These patches could be found in Eoan as well, mark this as fix-released.
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1830242
Title:
[linux-azure] Commits Requested in 16.04 for the Azure Kernel
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Bug description:
The 4.15 kernel require three patches for NVMe, those patches are
required to get to the target number of IOPS.
The commits are:
7ac257b862f2c (“blk-mq: remove the request_list usage”)
f9dde187fa921 ("nvme-pci: remove cq check after submission")
1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and
completion locks")
Please include these commits in the 4.15 based kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830242/+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 1759421] Re: linux-kvm VFIO support for Kata containers
** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1759421 Title: linux-kvm VFIO support for Kata containers Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Fix Released Bug description: Next configs are needed to support VFIO * CONFIG_DMAR_TABLE * CONFIG_HAVE_INTEL_TXT * CONFIG_INTEL_IOMMU * CONFIG_INTEL_IOMMU_DEFAULT_ON * CONFIG_INTEL_IOMMU_FLOPPY_WA * CONFIG_INTEL_IOMMU_SVM * CONFIG_IOMMU_API * CONFIG_IOMMU_IOVA * CONFIG_IOMMU_SUPPORT * CONFIG_IRQ_REMAP * CONFIG_PCI_ATS * CONFIG_PCI_PASID * CONFIG_VFIO * CONFIG_VFIO_IOMMU_TYPE1 * CONFIG_VFIO_PCI * CONFIG_VFIO_PCI_INTX * CONFIG_VFIO_PCI_MMAP * CONFIG_VFIO_VIRQFD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1759421/+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 1703742] Re: Transparent hugepages should default to enabled=madvise
** Changed in: linux-gke (Ubuntu) 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/1703742 Title: Transparent hugepages should default to enabled=madvise Status in linux package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-gke source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Bug description: SRU Justification, Zesty, Xenial [Impact] Ubuntu kernels should default transparent_hugepages to enabled=madvise, not enabled=always (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config). I've blogged about this at some length here: https://blog.nelhage.com/post/transparent-hugepages/ but here is a summary: Transparent Hugepages are a feature that allows the kernel to attempt to automatically back any anonymous maps with "huge" 2MiB page tables, instead of the normal 4k entries. It can produce small net performance gains in certain benchmarks, but also has numerous downsides, in the form of apparent memory leaks and 30% slowdowns or worse for some applications. Many popular pieces of software now refuse to run with hugepages enabled because of known performance issues. Examples of problem reports: MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/ Oracle: https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge Splunk: https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP Go runtime: https://github.com/golang/go/issues/8832 jemalloc: https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/ node.js: https://github.com/nodejs/node/issues/11077 Setting `enabled=madvise` enables applications that know they benefit from transparent huge pages to opt-in to this feature, while eliminating all the problematic behavior for other applications. Note also that transparent hugepage settings don't affect the use of explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …) [Fix] Enable CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Regression Potential] May marginally impact performance, but the benefits of madvise'd huge transparent hugepage over-weigh this considerably. This has been enabled in Artful since July (and in Bionic) and we've not seen any regression reports, so we are confident this has minimal impact. [Testcase] Kernel ADT tests and stress-ng memory tests should not show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+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
