| 2021-09-17 04:38:57 |
Khaled El Mously |
bug |
|
|
added bug |
| 2021-09-17 04:52:33 |
Khaled El Mously |
description |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential] |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential]
Low risk as the patches are mostly clean-up and refactor.
Regression in swiotlb could cause hardware read/write errors |
|
| 2021-09-17 04:52:42 |
Khaled El Mously |
bug task added |
|
linux-gcp (Ubuntu) |
|
| 2021-09-17 04:52:49 |
Khaled El Mously |
bug task deleted |
linux-oracle (Ubuntu) |
|
|
| 2021-09-17 04:53:05 |
Khaled El Mously |
nominated for series |
|
Ubuntu Focal |
|
| 2021-09-17 04:53:05 |
Khaled El Mously |
bug task added |
|
linux-gcp (Ubuntu Focal) |
|
| 2021-09-17 04:53:05 |
Khaled El Mously |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-09-17 04:53:05 |
Khaled El Mously |
bug task added |
|
linux-gcp (Ubuntu Bionic) |
|
| 2021-09-17 04:53:17 |
Khaled El Mously |
bug task added |
|
linux-gcp-5.4 (Ubuntu) |
|
| 2021-09-17 04:53:25 |
Khaled El Mously |
bug task deleted |
linux-gcp-5.4 (Ubuntu Focal) |
|
|
| 2021-09-17 04:53:31 |
Khaled El Mously |
bug task deleted |
linux-gcp (Ubuntu Bionic) |
|
|
| 2021-09-17 04:53:37 |
Khaled El Mously |
linux-gcp (Ubuntu): assignee |
|
Khaled El Mously (kmously) |
|
| 2021-09-17 04:53:39 |
Khaled El Mously |
linux-gcp-5.4 (Ubuntu): assignee |
|
Khaled El Mously (kmously) |
|
| 2021-09-17 04:53:42 |
Khaled El Mously |
linux-gcp (Ubuntu Focal): assignee |
|
Khaled El Mously (kmously) |
|
| 2021-09-17 04:53:43 |
Khaled El Mously |
linux-gcp-5.4 (Ubuntu Bionic): assignee |
|
Khaled El Mously (kmously) |
|
| 2021-09-17 04:54:35 |
Khaled El Mously |
description |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential]
Low risk as the patches are mostly clean-up and refactor.
Regression in swiotlb could cause hardware read/write errors |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential]
Low risk as the patches are mostly clean-up and refactor.
Regression in swiotlb could cause hardware read/write errors |
|
| 2021-09-17 05:09:57 |
Khaled El Mously |
description |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential]
Low risk as the patches are mostly clean-up and refactor.
Regression in swiotlb could cause hardware read/write errors |
See https://canonical.lightning.force.com/lightning/r/Case/5004K000009WBzrQAG/view for more info
[Impact]
Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors.
[Fix]
The following upstream patches from v5.12 address this:
3d2d861eb03e nvme-pci: set min_align_mask
1f221a0d0dbf swiotlb: respect min_align_mask
16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single
26a7e094783d swiotlb: refactor swiotlb_tbl_map_single
ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single
c32a77fd1878 swiotlb: factor out a nr_slots helper
c7fbeca757fe swiotlb: factor out an io_tlb_offset helper
b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define
[Test]
Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached:
$ sudo mkfs.xfs -f /dev/nvme2n1
meta-data=/dev/nvme2n1 isize=512 agcount=4, agsize=131072 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0, rmapbt=0, refl
ink=0
data = bsize=4096 blocks=524288, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite failed: Input/output error
Note the input/output error
The error no longer happens with the fixes applied.
[Regression Potential]
Low risk as the patches are mostly clean-up and refactor.
Regression in swiotlb could cause hardware read/write errors |
|
| 2021-09-21 07:12:04 |
Stefan Bader |
linux-gcp (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-09-21 07:12:11 |
Stefan Bader |
linux-gcp (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-09-21 07:12:20 |
Stefan Bader |
linux-gcp-5.4 (Ubuntu): status |
New |
Invalid |
|
| 2021-09-21 07:12:30 |
Stefan Bader |
linux-gcp (Ubuntu): status |
New |
Invalid |
|
| 2021-10-19 09:46:23 |
Launchpad Janitor |
linux-gcp (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2021-10-19 16:22:13 |
Launchpad Janitor |
linux-gcp-5.4 (Ubuntu Bionic): status |
New |
Fix Released |
|
