
18 Jun
2018
18 Jun
'18
4:48 a.m.
Brandon Allbery
I'd suspect it's mishandling the error return from a read(). Or not handling, but if the error it gets back is for some reason EAGAIN then it's kinda difficult to handle this sanely except by adding extra instrumentation to catch the loop.
If a selinux denial is producing EAGAIN, something is very wrong. I doubt that that’s what’s happening. If I knew where to go I could create a ticket…