| 2022-03-22 11:23:31 |
Sreekanth Reddy |
bug |
|
|
added bug |
| 2022-03-22 11:30:05 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-03-22 11:39:12 |
Sreekanth Reddy |
linux (Ubuntu): status |
Incomplete |
Opinion |
|
| 2022-04-07 15:54:38 |
Jeff Lane |
tags |
|
servcert-234 |
|
| 2022-04-07 15:59:19 |
Jeff Lane |
linux (Ubuntu): status |
Opinion |
New |
|
| 2022-04-07 16:00:05 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-06-07 04:17:15 |
Launchpad Janitor |
linux (Ubuntu): status |
Incomplete |
Expired |
|
| 2022-06-10 17:59:49 |
Jeff Lane |
linux (Ubuntu): status |
Expired |
Confirmed |
|
| 2022-08-15 15:32:36 |
Michael Reed |
linux (Ubuntu): assignee |
|
Michael Reed (mreed8855) |
|
| 2022-08-16 17:28:51 |
Jeff Lane |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2022-08-17 00:51:10 |
Michael Reed |
linux (Ubuntu): status |
Incomplete |
In Progress |
|
| 2022-08-17 00:51:17 |
Michael Reed |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-08-17 00:51:24 |
Michael Reed |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-08-17 00:51:24 |
Michael Reed |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2022-08-17 00:51:36 |
Michael Reed |
linux (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-08-17 00:51:42 |
Michael Reed |
linux (Ubuntu Jammy): assignee |
|
Michael Reed (mreed8855) |
|
| 2022-09-27 15:34:56 |
Michael Reed |
description |
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data. |
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
[Fix]
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data.
[Test Plan]
1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.
[Where problems could occur]
[Other Info] |
|
| 2022-09-27 15:50:19 |
Michael Reed |
description |
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
[Fix]
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data.
[Test Plan]
1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.
[Where problems could occur]
[Other Info] |
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
[Fix]
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data.
[Test Plan]
1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 |
|
| 2022-10-07 12:45:18 |
Stefan Bader |
linux (Ubuntu Jammy): importance |
Undecided |
Medium |
|
| 2022-10-07 12:45:24 |
Stefan Bader |
linux (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-10-18 14:32:29 |
Michael Reed |
tags |
servcert-234 |
servcert-234 verification-done-jammy |
|
| 2022-10-18 14:33:41 |
Michael Reed |
description |
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
[Fix]
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data.
[Test Plan]
1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 |
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface
[Fix]
Below is the summary of each of the above bug fix commits,
1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not.
2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"
3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region.
Please let me if I have missed to add any data.
[Test Plan]
1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.
[Where problems could occur]
The regression risk is low.
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927 |
|
| 2022-11-15 10:52:08 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-11-15 10:52:08 |
Launchpad Janitor |
cve linked |
|
2022-2978 |
|
| 2022-11-15 10:52:08 |
Launchpad Janitor |
cve linked |
|
2022-3028 |
|
| 2022-11-15 10:52:08 |
Launchpad Janitor |
cve linked |
|
2022-40768 |
|
| 2022-12-07 15:49:23 |
Ubuntu Kernel Bot |
tags |
servcert-234 verification-done-jammy |
kernel-spammed-jammy-linux-bluefield servcert-234 verification-needed-jammy |
|
| 2022-12-12 12:46:39 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-bluefield servcert-234 verification-needed-jammy |
kernel-spammed-jammy-linux-bluefield kernel-spammed-jammy-linux-nvidia servcert-234 verification-needed-jammy |
|
| 2023-08-09 15:39:30 |
Michael Reed |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2024-03-01 06:16:13 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-bluefield kernel-spammed-jammy-linux-nvidia servcert-234 verification-needed-jammy |
kernel-spammed-jammy-linux-bluefield kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia servcert-234 verification-needed-jammy verification-needed-jammy-linux-mtk |
|
| 2024-03-05 09:32:56 |
Ranjan Kumar |
bug |
|
|
added subscriber Ranjan Kumar |
