arm64: fix exec() deadlock by releasing ext2 lock before userspace jump #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
exec()run_userspace_from_ext2()held ext2 lock across non-returning ERET to userspacedrop(fs_guard)after ELF read, before userspace jumpRoot Cause Analysis
run_userspace_from_ext2()acquiresext2::root_fs()spinlockexec()deadlock trying to acquire the same lockChanges
kernel/src/main_aarch64.rs: Adddrop(fs_guard)after ELF data readkernel/src/arch_impl/aarch64/trace.rs: Lock-free trace buffer for debuggingkernel/src/arch_impl/aarch64/syscall_entry.rs: Trace points for exec patharm64-parity.md: ARM64 parity tracking documentTest plan
🤖 Generated with Claude Code