Update of bug #61043 (project groff):
Privacy: Private => Public
_______________________________________________________
Follow-up Comment #4:
Setting "privacy" to "public".
I don't think this issue is a sensitive one. I perceive no confidentiality or
integrity violations here. The issue is one of availability--there are
innumerable ways in unprivileged code on POSIX systems to busy-wait, and crude
tools like resource limits to manage that problem.
So, in my opinion, this is an ordinary bug.
Also, since I already pushed commits with detailed information, the horse is
out of the principled barn.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61043>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
