25 Jan
2023
25 Jan
'23
9:08 a.m.
On Wednesday, January 25, 2023 10:05:36 AM CET, Andrew Randrianasulu wrote:
Just for making things more clear: *I* added this unlock, not because I knew what I was doing but simply because yeah, it looked like this place might need it.
In theory oicks protects shared resources, so one thread may leave object/variable around without worry another thread scheduled by kernel will overwrite it.
But I do not know enough of details for carelessly altering locking like I did. So, Phyllis removed this line on my request, because, I reiterate, I put it there literally on a whim.
I think you did fix a bug at this place, and I wonder how total lock would get unlocked (other than maybe time out?). -- Stefan