Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#69491 - [linux] NFS kernel regression, consider reverting it in our package

Attached to Project: Arch Linux
Opened by John (graysky) - Sunday, 31 January 2021, 22:05 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:08 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


A regression introduced in 5.10.11 affecting NFS hit at least one use-case documented here[1]. In short, the regression causes read file errors through libnfs. In my use case, kodi reading data from NFS was unable to read media. Kodi devs will be handling the upstream bug report.

After bisecting, the offensive commit is 00ee972739fb2526d3936f1e7ccfc8c91d250c60. I built our 5.10.12-1 kernel package reverting the offending commit which restored functionality. I opened this task to get eyes on this sooner than later.

This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 21 April 2021, 10:08 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Monday, 01 February 2021, 22:39 GMT
[1] The link to linux-nfs for the backport to 5.10 and [2] link for the original commit.
Not sure if the commit should not have been backported or if the original commit is the issue you would need to test 5.11-rc4+

Comment by John (graysky) - Wednesday, 03 February 2021, 12:47 GMT Comment by loqs (loqs) - Wednesday, 03 February 2021, 14:14 GMT
Has upstream been notified and agreed it should be reverted?
Have you check 5.11-rc4+ to see if 4a85a6a3320b4a622315d2e0ea91a1d2b013bce4 should be reverted before 5.11 is released?
Comment by Mike Javorski (javmorin) - Friday, 05 February 2021, 18:20 GMT Comment by John (graysky) - Friday, 05 February 2021, 19:30 GMT
@javmorin - I applied to our 5.10.13 package and it seems to fix the original issue. Thanks for posting. Hopefully it gets back ported soon.
Comment by John (graysky) - Monday, 08 February 2021, 08:33 GMT