[Kernel-packages] [Bug 1981105] Re: i2c-mlxbf.c: support lock mechanism
This bug was fixed in the package linux-bluefield - 5.4.0-1045.50 --- linux-bluefield (5.4.0-1045.50) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1045.50 -proposed tracker (LP: #1983921) * pwr-mlxbf.c: Improve driver dependencies and fix zero allocating memory size (LP: #1980750) - SAUCE: pwr-mlxbf.c: Improve driver dependencies - SAUCE: pwr-mlxbf.c: Fix zero allocating memory size - SAUCE: pwr-mlxbf.c: Update driver version to 1.1 * store the last executed chain also for clsact egress (LP: #1982980) - net/sched: store the last executed chain also for clsact egress * i2c-mlxbf.c: support lock mechanism (LP: #1981105) - SAUCE: i2c-mlxbf.c: support lock mechanism * i2c-mlxbf.c: fix wrong variable name (LP: #1982357) - SAUCE: i2c-mlxbf.c: fix wrong variable name [ Ubuntu: 5.4.0-125.141 ] * focal/linux: 5.4.0-125.141 -proposed tracker (LP: #1983947) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - blk-mq: blk-mq: provide forced completion method - blk-mq: move failure injection out of blk_mq_complete_request - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * CVE-2021-33656 - vt: drop old FONT ioctls * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state -- Zachary Tahenakos Thu, 11 Aug 2022 15:11:51 -0400 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33656 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change because at boot time ATF will ensure that the lock is released. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. Make sure you load the latest ATF/UEFI image to accompany this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981105] Re: i2c-mlxbf.c: support lock mechanism
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change because at boot time ATF will ensure that the lock is released. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. Make sure you load the latest ATF/UEFI image to accompany this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981105] Re: i2c-mlxbf.c: support lock mechanism
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change because at boot time ATF will ensure that the lock is released. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. Make sure you load the latest ATF/UEFI image to accompany this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981105] Re: i2c-mlxbf.c: support lock mechanism
** Description changed: SRU Justification: [Impact] - Support the I2C lock mechanism, otherwise there could be unexpected - behavior when an i2c bus is accessed by several entities like the linux - driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap - since it is deprecated in later kernels. + Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change + because at boot time ATF will ensure that the lock is released. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. + Make sure you load the latest ATF/UEFI image to accompany this change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change because at boot time ATF will ensure that the lock is released. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. Make sure you load the latest ATF/UEFI image to accompany this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981105] Re: i2c-mlxbf.c: support lock mechanism
** Description changed: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected - behavior when the i2c driver is accessed by several entities like the - linux driver, ATF driver and UEFI driver. + behavior when an i2c bus is accessed by several entities like the linux + driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap + since it is deprecated in later kernels. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1981105 Title: i2c-mlxbf.c: support lock mechanism Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap since it is deprecated in later kernels. [Fix] * Support lock and unlock * replace ioremap_nocache with ioremap [Test Case] * Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created * check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course) [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1981105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
