patacongo commented on PR #11226: URL: https://github.com/apache/nuttx/pull/11226#issuecomment-1819872293
What if multiple tasks running on different CPUs lock the scheduler? This is the legacy behavior. Seems to me that there is a hole in the logic for this case. We can't suspend the task in that case or we break to critical use case of the lock. That has been supported in the past and is the whole reason for the bit set of locks. With this change. If one task locks the scheduler, do all of the other tasks get suspended, losing the ability to have multiple locks? If that is the case, is there a race condition for taking the lock? Couldn't you still end up with mutliple task holding the lock (although all be once would be suspended). Changing the model of how the scheduler locks work like this might have implications that we are unaware of. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
