[Group.of.nepali.translators] [Bug 1856949] Re: cifs: kernel NULL pointer dereference, address: 0000000000000038
** Description changed:
- [598428.945633] BUG: kernel NULL pointer dereference, address:
0038
- ...
- [598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
- [598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
- ...
- [598428.945834] Call Trace:
- [598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
- [598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
- [598428.945909] process_one_work+0x1db/0x380
- [598428.945914] worker_thread+0x4d/0x400
- [598428.945921] kthread+0x104/0x140
- [598428.945925] ? process_one_work+0x380/0x380
- [598428.945931] ? kthread_park+0x80/0x80
- [598428.945937] ret_from_fork+0x35/0x40
+ [Impact]
+
+ Currently when the client creates a cifsFileInfo structure for
+ a newly opened file, it allocates a list of byte-range locks
+ with a pointer to the new cfile and attaches this list to the
+ inode's lock list. The latter happens before initializing all
+ other fields, e.g. cfile->tlink. Thus a partially initialized
+ cifsFileInfo structure becomes available to other threads that
+ walk through the inode's lock list. One example of such a thread
+ may be an oplock break worker thread that tries to push all
+ cached byte-range locks. This causes NULL-pointer dereference
+ in smb2_push_mandatory_locks() when accessing cfile->tlink:
+
+ [598428.945633] BUG: kernel NULL pointer dereference, address:
0038
+ ...
+ [598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
+ [598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
+ ...
+ [598428.945834] Call Trace:
+ [598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
+ [598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
+ [598428.945909] process_one_work+0x1db/0x380
+ [598428.945914] worker_thread+0x4d/0x400
+ [598428.945921] kthread+0x104/0x140
+ [598428.945925] ? process_one_work+0x380/0x380
+ [598428.945931] ? kthread_park+0x80/0x80
+ [598428.945937] ret_from_fork+0x35/0x40
+
+
+ [Test Case]
+
+ TBD.
+
+
+ [Fix]
+
+ Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
+ NULL-pointer dereference in smb2_push_mandatory_locks")
+
+ [Regression Potential]
+
+ Low. The patch is fairly simple and it's tagged for stable kernels. In
+ fact it is already in some of the released upstream stable kernels.
** No longer affects: linux (Ubuntu Focal)
--
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/1856949
Title:
cifs: kernel NULL pointer dereference, address: 0038
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address:
0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe :
[Group.of.nepali.translators] [Bug 1856896] Re: Only check the vendor ID if the device has one set
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- 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/1856896 Title: Only check the vendor ID if the device has one set Status in OEM Priority Project: Confirmed Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Invalid Status in fwupd source package in Bionic: New Status in fwupd source package in Disco: Won't Fix Status in fwupd source package in Eoan: New Status in fwupd source package in Focal: Fix Released Bug description: [Impact] fwupd will fail to install firmware where the firmware has a vendor-id but the device does not have one set. The vendor-id is currently optional but in about 6 months time it will be required. In this case devices that can't store vendor-ids will not be able to install firmware. There is an upstream fix to skip this check if the device doesn't have vendor IDs. https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] There's not a specific test case for this, as no firmware currently meets this requirement. Thus the only test is that you can still successfully install firmware. Future firmware will trigger this case. [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856896/+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 1856896] Re: Only check the vendor ID if the device has one set
I've made an upload that should be able to replace the existing SRU and get them both checked. I've also checked the fwupd 0.8 source and am pretty sure this doesn't have the check there to be updated. ** Changed in: fwupd (Ubuntu Xenial) 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/1856896 Title: Only check the vendor ID if the device has one set Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Invalid Status in fwupd source package in Bionic: New Status in fwupd source package in Disco: Won't Fix Status in fwupd source package in Eoan: New Status in fwupd source package in Focal: Fix Released Bug description: [Impact] fwupd will fail to install firmware where the firmware has a vendor-id but the device does not have one set. The vendor-id is currently optional but in about 6 months time it will be required. In this case devices that can't store vendor-ids will not be able to install firmware. There is an upstream fix to skip this check if the device doesn't have vendor IDs. https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] There's not a specific test case for this, as no firmware currently meets this requirement. Thus the only test is that you can still successfully install firmware. Future firmware will trigger this case. [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1856896/+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 1856896] Re: Only check the vendor ID if the device has one set
** Description changed: [Impact] fwupd will fail to install firmware where the firmware has a vendor-id but the device does not have one set. The vendor-id is currently optional but in about 6 months time it will be required. In this case devices that can't store vendor-ids will not be able to install firmware. There is an upstream fix to skip this check if the device doesn't have vendor IDs. https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] + There's not a specific test case for this, as no firmware currently meets this requirement. Thus the only test is that you can still successfully install firmware. Future firmware will trigger this case. [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. ** Changed in: fwupd (Ubuntu Disco) Status: New => Won't Fix ** Changed in: fwupd (Ubuntu Disco) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1856896 Title: Only check the vendor ID if the device has one set Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: New Status in fwupd source package in Bionic: New Status in fwupd source package in Disco: Won't Fix Status in fwupd source package in Eoan: New Status in fwupd source package in Focal: Fix Released Bug description: [Impact] fwupd will fail to install firmware where the firmware has a vendor-id but the device does not have one set. The vendor-id is currently optional but in about 6 months time it will be required. In this case devices that can't store vendor-ids will not be able to install firmware. There is an upstream fix to skip this check if the device doesn't have vendor IDs. https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] There's not a specific test case for this, as no firmware currently meets this requirement. Thus the only test is that you can still successfully install firmware. Future firmware will trigger this case. [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1856896/+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 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1854828 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/1854829 Title: xenial/linux-raspi2: 4.4.0-1127.136 -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: In Progress 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1854828 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+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 1854801] Re: xenial/linux-aws-hwe: 4.15.0-1057.59~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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Friday, 06. December 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-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/1854801 Title: xenial/linux-aws-hwe: 4.15.0-1057.59~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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Friday, 06. December 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854801/+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 1856896] [NEW] Only check the vendor ID if the device has one set
Public bug reported: [Impact] https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. ** Affects: fwupd (Ubuntu) Importance: High Status: Fix Released ** Affects: fwupd (Ubuntu Xenial) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: fwupd (Ubuntu Bionic) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: fwupd (Ubuntu Disco) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: fwupd (Ubuntu Eoan) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: fwupd (Ubuntu Focal) Importance: High Status: Fix Released ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Focal) Status: New => Fix Released ** Changed in: fwupd (Ubuntu Eoan) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Disco) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: fwupd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: fwupd (Ubuntu Disco) Importance: Medium => High ** Changed in: fwupd (Ubuntu Eoan) Importance: Undecided => High ** Changed in: fwupd (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Focal) Importance: Undecided => High ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1856896 Title: Only check the vendor ID if the device has one set Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: New Status in fwupd source package in Bionic: New Status in fwupd source package in Disco: New Status in fwupd source package in Eoan: New Status in fwupd source package in Focal: Fix Released Bug description: [Impact] https://github.com/fwupd/fwupd/commit/d5f965da2f8847e494e5c2a25a123bb8c31c7850 [Test Case] [Regression Potential] Change is simple and unlikely to introduce a significant bug. This will cause a behaviour change, but it is done by the upstream maintainer and intentional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1856896/+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 1854801] Re: xenial/linux-aws-hwe: 4.15.0-1057.59~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Friday, 06. December 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-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/1854801 Title: xenial/linux-aws-hwe: 4.15.0-1057.59~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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Friday, 06. December 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854801/+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 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker
** 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: 1854819 + kernel-stable-master-bug: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs ** Changed in: kernel-sru-workflow/regression-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 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/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+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 1854832] Re: xenial/linux-fips: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 05. December 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-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/1854832 Title: xenial/linux-fips: 4.4.0-1027.32 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1854835 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 05. December 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854832/+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 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-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/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+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 1856851] [NEW] rustc 1.39 and cargo 0.40 required by firefox 73
Public bug reported: Firefox 73+ will require rustc 1.39 and cargo 0.40 to build¹. The beta phase for Firefox 73.0 begins on 2020-01-02 and release candidates will be available from 2020-02-06. We will need these in focal and all supported releases (xenial, bionic and eoan). No need to support disco as it will be EOL before firefox 73.0 is released. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1594538 ** Affects: cargo (Ubuntu) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: Confirmed ** Affects: rustc (Ubuntu) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: Confirmed ** Affects: cargo (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Affects: rustc (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Affects: cargo (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: rustc (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: cargo (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Affects: rustc (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Also affects: cargo (Ubuntu) Importance: Undecided Status: New ** Changed in: cargo (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: rustc (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Also affects: cargo (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Disco) Importance: Undecided Status: New ** No longer affects: rustc (Ubuntu Disco) ** No longer affects: cargo (Ubuntu Disco) ** Description changed: Firefox 73+ will require rustc 1.39 and cargo 0.40 to build¹. The beta phase for Firefox 73.0 begins on 2020-01-02 and release candidates will be available from 2020-02-06. - We will need these in focal and all supported releases (xenial, bionic, - disco and eoan). + We will need these in focal and all supported releases (xenial, bionic + and eoan). No need to support disco as it will be EOL before firefox + 73.0 is released. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1594538 -- 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/1856851 Title: rustc 1.39 and cargo 0.40 required by firefox 73 Status in cargo package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in cargo source package in Xenial: Confirmed Status in rustc source package in Xenial: Confirmed Status in cargo source package in Bionic: Confirmed Status in rustc source package in Bionic: Confirmed Status in cargo source package in Eoan: Confirmed Status in rustc source package in Eoan: Confirmed Bug description: Firefox 73+ will require rustc 1.39 and cargo 0.40 to build¹. The beta phase for Firefox 73.0 begins on 2020-01-02 and release candidates will be available from 2020-02-06. We will need these in focal and all supported releases (xenial, bionic and eoan). No need to support disco as it will be EOL before firefox 73.0 is released. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1594538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1856851/+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 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu Cosmic)
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/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
New
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+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
