On Tue, Sep 15, 2020 at 06:34:21PM -0400, Mark H Weaver wrote: > That's useful information, but we should not stay frozen on the 5.8.7 > kernel for much longer. 5.8.8 contains many bug fixes, some of which > might fix potentially exploitable flaws. > > It would be useful to know if this problem still occurs with 5.8.9, > which has since come out. If so, we should do a bisection between 5.8.7 > and 5.8.8 to find out which upstream commit introduced the problem. > > Would anyone like to investigate this further?
I will try to reproduce the bug with 5.8.9 now. I will try the bisection if time permits.
