For future reference, the mentioned patch git merged upstream, as commit 9da5a1092b13468839b1a864b126cacfb72ad016
It also made it into stable, 4.12.4 I believe, as 5cc9b698a494827b15f74ef70a31d7911d00e52a
So I think this should be fixed (or at least better) in F26, because we currently ship 4.12.5-300.fc26.x86_64
For future reference, the mentioned patch git merged upstream, as commit 9da5a1092b13468 839b1a864b126ca cfb72ad016 b15f74ef70a31d7 911d00e52a
It also made it into stable, 4.12.4 I believe, as 5cc9b698a494827
So I think this should be fixed (or at least better) in F26, because we currently ship 4.12.5- 300.fc26. x86_64