hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk

Bug #1702253 reported by Zhanglei Mao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

The user upgrade Ubuntu server to linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of ES3000 V2 SSD which the correspond module driver of hio.ko is include in this kernel. The data write to disk seems was incorrect.

To format this sdd disk with xfs get error of "meta data corruption" and to use dd write data to this ssd disk and read out again, the sha256 chuksum is also mismatched.

It was tested for 4.8.0-34-generic, 4.10.0-26-generic and 4.12, this problem was not found on 4.8.0-34-generic, but both 4.10.0-26-generic and 4.12 have same issues.

This hio source can be download from http://support.huawei.com/enterprise/zh/server/es3000-v2-pid-21242728/software/22305278?idAbsPath=fixnode01%7C7919749%7C9856522%7C9856629%7C21462722%7C21242728. It is also include in Ubuntu kernel tree of linux-source-4.10.0.

Huawei reports that they get similar problem when upgrading from linux4.4 to linux4.8 and they fix it at the hio driver in 2.1.0.28 version as:
The modification for 4.8 is as below:
        if (!test_bit(SSD_ONLINE, &dev->state)) {
                ssd_bio_endio(bio, -ENODEV);
                goto out;
        }

#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
        blk_queue_split(q, &bio, q->bio_split);
#endif

Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1702253

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1702253

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

It is Ubuntu server without Desktop environment and I can't provide my launchpad access to customer too.

I will ask them to collect bug reports by:
apport-bug linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb

I am not family for apport. Can apport-bug provide what you want?

Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

We found same problem on Ubuntu17.04 the kernel version is linux-image-4.10.0-19-generic上. The apport report is in the attachment file.

We compared and testing on kernel 4.9 an 4.10, this HIO driver works fine on 4.9 but does not work
on kernel 4.10-rc5 and aboe.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

Huawei have fix this bug and provide patch to our team that will be merged in 4.12.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.