Comment 17 for bug 1896578

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Hi Evan,

The patches have been submitted for SRU to the Ubuntu kernel mailing list, for the 4.15, 5.4, 5.8 and 5.11 kernels:

[0] https://lists.ubuntu.com/archives/kernel-team/2021-May/119935.html
[1] https://lists.ubuntu.com/archives/kernel-team/2021-May/119936.html
[2] https://lists.ubuntu.com/archives/kernel-team/2021-May/119937.html
[3] https://lists.ubuntu.com/archives/kernel-team/2021-May/119938.html
[4] https://lists.ubuntu.com/archives/kernel-team/2021-May/119939.html
[5] https://lists.ubuntu.com/archives/kernel-team/2021-May/119941.html
[6] https://lists.ubuntu.com/archives/kernel-team/2021-May/119940.html
[7] https://lists.ubuntu.com/archives/kernel-team/2021-May/119942.html
[8] https://lists.ubuntu.com/archives/kernel-team/2021-May/119943.html
[9] https://lists.ubuntu.com/archives/kernel-team/2021-May/119944.html
[10] https://lists.ubuntu.com/archives/kernel-team/2021-May/119945.html
[11] https://lists.ubuntu.com/archives/kernel-team/2021-May/119946.html

The kernel team have reviewed the patches, but they are in no hurry to ACK the patchset [12], and they also haven't outright rejected it.

[12] https://lists.ubuntu.com/archives/kernel-team/2021-May/120051.html

The current status is that the kernel team have requested more testing to be performed, and that the patches will not make the current SRU cycle. They will instead be submitted for consideration in the next SRU cycle.

You can look at https://kernel.ubuntu.com/ for dates of various SRU cycles. If the patches are accepted for the 2021.05.31 SRU cycle, then you could expect a supported kernel to be available in late June.

If you want to help, then please consider installing the test kernels in comment #14 and helping test Raid10 on ssds / NVMe drives that support block discard.

I am currently using a cloud instance with 4x NVMe disks in Raid10 as my /home directory, and things seem okay.

I'll keep you updated on the progress of this patchset via this bug.

Thanks,
Matthew