| 2017-06-29 16:09:24 |
Peter Sabaini |
bug |
|
|
added bug |
| 2017-06-29 16:09:24 |
Peter Sabaini |
attachment added |
|
apport.linux-image-4.10.0-26-generic.yd28tuoe.apport https://bugs.launchpad.net/bugs/1701316/+attachment/4905802/+files/apport.linux-image-4.10.0-26-generic.yd28tuoe.apport |
|
| 2017-06-29 16:10:43 |
Launchpad Janitor |
linux (Ubuntu): status |
New |
Confirmed |
|
| 2017-06-29 16:11:16 |
Peter Sabaini |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2017-07-03 05:37:22 |
Junien Fridrick |
bug |
|
|
added subscriber Junien Fridrick |
| 2017-07-05 16:21:59 |
Seth Forshee |
bug |
|
|
added subscriber Seth Forshee |
| 2017-07-06 13:37:43 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2017-07-06 13:38:07 |
Joseph Salisbury |
tags |
canonical-bootstack |
canonical-bootstack kernel-key |
|
| 2017-07-06 14:58:05 |
Brad Figg |
linux (Ubuntu): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-07-07 08:26:40 |
Jonas Andrén |
bug |
|
|
added subscriber Jonas Andrén |
| 2017-07-07 13:07:01 |
Seth Forshee |
nominated for series |
|
Ubuntu Artful |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-07-07 13:07:01 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Yakkety) |
|
| 2017-07-07 13:07:23 |
Seth Forshee |
linux (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-07-07 13:07:23 |
Seth Forshee |
linux (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-07-07 13:07:23 |
Seth Forshee |
linux (Ubuntu Xenial): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-07-07 13:07:34 |
Seth Forshee |
linux (Ubuntu Yakkety): status |
New |
In Progress |
|
| 2017-07-07 13:07:34 |
Seth Forshee |
linux (Ubuntu Yakkety): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-07-07 13:07:42 |
Seth Forshee |
linux (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2017-07-07 13:07:52 |
Seth Forshee |
linux (Ubuntu Zesty): importance |
Undecided |
High |
|
| 2017-07-07 13:07:52 |
Seth Forshee |
linux (Ubuntu Zesty): status |
New |
In Progress |
|
| 2017-07-07 13:07:52 |
Seth Forshee |
linux (Ubuntu Zesty): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-07-07 13:08:00 |
Seth Forshee |
linux (Ubuntu Artful): status |
Confirmed |
In Progress |
|
| 2017-07-07 13:12:29 |
Seth Forshee |
linux (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2017-07-07 13:12:43 |
Seth Forshee |
linux (Ubuntu Xenial): status |
In Progress |
Invalid |
|
| 2017-07-10 15:35:09 |
Joseph Salisbury |
tags |
canonical-bootstack kernel-key |
canonical-bootstack |
|
| 2017-07-11 12:05:52 |
Seth Forshee |
description |
We are seeing data corruption issues using the hio driver with kernel 4.10.0
# uname -a
Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Making xfs fails:
root@arbok:~# mkfs.xfs /dev/hioa
meta-data=/dev/hioa isize=512 agcount=4, agsize=48835584 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0
data = bsize=4096 blocks=195342336, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=95382, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
bad magic number
bad magic number
Metadata corruption detected at xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
The drive appears to be healthy. Firmware has been upgraded to ver 656:
root@arbok:~# hio_info -d /dev/hioa
hioa Serial number: 022XWV10G2000325
Size(GB): 800
Max size(GB): 800
Hardware version: 1.0
Firmware version: 656
Driver version: 2.1.0.28
Work mode: MLC
Run time (sec.): 8910490
Total read(MB): 8499
Total write(MB): 0
Lifetime remaining: 99.844%
Max bad block rate: 0.167%
Health: OK
Comment: NA
No relevant entries about read/write errors in dmesg
Also just copying 8G random data and reading those back gives a hash mismatch:
root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
sha256sum test.dat read-
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
root@arbok:~# sha256sum test.dat read-back.dat
6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat
ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat |
Impact: Data corruption is seen when using the hio driver with 4.8 and later kernels.
Fix: Patch to fix incorrect use of enumerated values as bitmasks.
Test case: See below.
Regression potential: Very low. Changes are simple and Obviously Correct (TM), and they only affect the hio driver.
---
We are seeing data corruption issues using the hio driver with kernel 4.10.0
# uname -a
Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Making xfs fails:
root@arbok:~# mkfs.xfs /dev/hioa
meta-data=/dev/hioa isize=512 agcount=4, agsize=48835584 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0
data = bsize=4096 blocks=195342336, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=95382, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
bad magic number
bad magic number
Metadata corruption detected at xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
The drive appears to be healthy. Firmware has been upgraded to ver 656:
root@arbok:~# hio_info -d /dev/hioa
hioa Serial number: 022XWV10G2000325
Size(GB): 800
Max size(GB): 800
Hardware version: 1.0
Firmware version: 656
Driver version: 2.1.0.28
Work mode: MLC
Run time (sec.): 8910490
Total read(MB): 8499
Total write(MB): 0
Lifetime remaining: 99.844%
Max bad block rate: 0.167%
Health: OK
Comment: NA
No relevant entries about read/write errors in dmesg
Also just copying 8G random data and reading those back gives a hash mismatch:
root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
sha256sum test.dat read-
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
root@arbok:~# sha256sum test.dat read-back.dat
6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat
ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat |
|
| 2017-07-11 12:17:55 |
Seth Forshee |
description |
Impact: Data corruption is seen when using the hio driver with 4.8 and later kernels.
Fix: Patch to fix incorrect use of enumerated values as bitmasks.
Test case: See below.
Regression potential: Very low. Changes are simple and Obviously Correct (TM), and they only affect the hio driver.
---
We are seeing data corruption issues using the hio driver with kernel 4.10.0
# uname -a
Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Making xfs fails:
root@arbok:~# mkfs.xfs /dev/hioa
meta-data=/dev/hioa isize=512 agcount=4, agsize=48835584 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0
data = bsize=4096 blocks=195342336, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=95382, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
bad magic number
bad magic number
Metadata corruption detected at xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
The drive appears to be healthy. Firmware has been upgraded to ver 656:
root@arbok:~# hio_info -d /dev/hioa
hioa Serial number: 022XWV10G2000325
Size(GB): 800
Max size(GB): 800
Hardware version: 1.0
Firmware version: 656
Driver version: 2.1.0.28
Work mode: MLC
Run time (sec.): 8910490
Total read(MB): 8499
Total write(MB): 0
Lifetime remaining: 99.844%
Max bad block rate: 0.167%
Health: OK
Comment: NA
No relevant entries about read/write errors in dmesg
Also just copying 8G random data and reading those back gives a hash mismatch:
root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
sha256sum test.dat read-
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
root@arbok:~# sha256sum test.dat read-back.dat
6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat
ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat |
Impact: Data corruption is seen when using the hio driver with 4.10 and later kernels.
Fix: Patch to fix incorrect use of enumerated values as bitmasks.
Test case: See below.
Regression potential: Very low. Changes are simple and Obviously Correct (TM), and they only affect the hio driver.
---
We are seeing data corruption issues using the hio driver with kernel 4.10.0
# uname -a
Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Making xfs fails:
root@arbok:~# mkfs.xfs /dev/hioa
meta-data=/dev/hioa isize=512 agcount=4, agsize=48835584 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=0
data = bsize=4096 blocks=195342336, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal log bsize=4096 blocks=95382, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
bad magic number
bad magic number
Metadata corruption detected at xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
The drive appears to be healthy. Firmware has been upgraded to ver 656:
root@arbok:~# hio_info -d /dev/hioa
hioa Serial number: 022XWV10G2000325
Size(GB): 800
Max size(GB): 800
Hardware version: 1.0
Firmware version: 656
Driver version: 2.1.0.28
Work mode: MLC
Run time (sec.): 8910490
Total read(MB): 8499
Total write(MB): 0
Lifetime remaining: 99.844%
Max bad block rate: 0.167%
Health: OK
Comment: NA
No relevant entries about read/write errors in dmesg
Also just copying 8G random data and reading those back gives a hash mismatch:
root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
sha256sum test.dat read-
8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
root@arbok:~# sha256sum test.dat read-back.dat
6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat
ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat |
|
| 2017-07-14 15:14:45 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-07-14 15:20:04 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2017-07-21 09:25:16 |
Kleber Sacilotto de Souza |
tags |
canonical-bootstack |
canonical-bootstack verification-needed-zesty |
|
| 2017-07-26 15:23:42 |
Andy Whitcroft |
linux (Ubuntu Yakkety): status |
Fix Committed |
Won't Fix |
|
| 2017-08-02 12:34:35 |
Peter Sabaini |
tags |
canonical-bootstack verification-needed-zesty |
canonical-bootstack verification-done-zesty |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
cve linked |
|
2017-1000364 |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
cve linked |
|
2017-1000365 |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
cve linked |
|
2017-10810 |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
cve linked |
|
2017-7482 |
|
| 2017-08-03 16:29:32 |
Launchpad Janitor |
cve linked |
|
2017-7533 |
|
| 2017-08-10 05:56:17 |
Launchpad Janitor |
linux (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
