There's a certain peculiar kind of pleasure in exploring the boundaries of a bug to refine it down to what's essential to reproduce it versus what's just incidental. Do I need to hold the file open? Yes. Do I have to fstat() it? Nope. Is having the file opened read-write important? Turns out, yes.


What's fascinating about this particular kernel bug to me is how clearly I can see the kernel's implementation poking through in what the bug is and what's required to reproduce it. The more I refine things, the more I can guess where the problem probably is.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!