---
Regards,
K.R. Foley
On 2020-11-20 13:42, Randy Dunlap wrote:
On 11/20/20 11:16 AM, K.R. Foley wrote:
I have found an issue that triggers by running lsof. The problem is
reproducible, but not consistently. I have seen this issue occur on
multiple versions of the kernel (5.0.10, 5.2.8 and now 5.4.77). It
looks like it could be a race condition or the file pointer is being
corrupted. Any pointers on how to track this down? What additional
information can I provide?
Hi,
2 things in general:
a) Can you test with a more recent kernel?
b) Can you reproduce this without loading the proprietary & out-of-tree
kernel modules? They should never have been loaded after bootup.
I.e., don't just unload them -- that could leave something bad behind.
I can try to reproduce with a newer kernel and without the modules.
