kernel: fixup current_thread==0 on resume

For some reason, the current thread becomes 0 during suspend or resume.
This causes an error during boot.

Patch this up while we figure out what's causing it.

Signed-off-by: Sean Cross <sean@xobs.io>
This commit is contained in:
Sean Cross 2023-01-31 16:01:35 +08:00
parent abb1455fe6
commit 1303e6416d

View file

@ -587,7 +587,11 @@ impl SystemServices {
let mut current = self
.get_process_mut(current_pid)
.expect("couldn't get current PID");
assert!(arch::process::current_tid() == current.current_thread);
// The current thread should never be 0, but for some reason it ends up
// as 0 after resuming from suspend. It's unclear how this happens.
if current.current_thread == 0 {
current.current_thread = arch::process::current_tid();
}
// let old_state = current.state;
current.state = match current.state {
ProcessState::Running(x) => ProcessState::Ready(x | (1 << current.current_thread)),