@jsalisbury
Current trusty 3.13.0-34 is affected.
I then tested latest 3.13.0-35 from trusty proposed repository and the bug is still there.
Even 3.13.0-35.62 from trusty git repo suffers from the same bug.
Unsurprisingly, mainline 3.13.11.6 is not affected by this bug at all.
@jsalisbury
Current trusty 3.13.0-34 is affected.
I then tested latest 3.13.0-35 from trusty proposed repository and the bug is still there.
Even 3.13.0-35.62 from trusty git repo suffers from the same bug.
Unsurprisingly, mainline 3.13.11.6 is not affected by this bug at all.