Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maybe unsound in free_mutex #58

Open
lwz23 opened this issue Dec 11, 2024 · 1 comment
Open

Maybe unsound in free_mutex #58

lwz23 opened this issue Dec 11, 2024 · 1 comment

Comments

@lwz23
Copy link

lwz23 commented Dec 11, 2024

Hello, thank you for your contribution in this project, I am scanning the unsoundness problem in rust project.
I notice the following code:

pub fn free_mutex(mutex: *mut KMutex) {
        let index = unsafe { mutex.offset_from(&rust_mutex_pool[0] as *const _) } as usize;
        let byte = index / 8;
        let bit = index % 8;
        USED[byte].fetch_and(!(1 << bit), Ordering::Relaxed);
    }

Considering that pub mod mutex_alloc, and free_mutex is also a pub function. I assume that users can directly call this function. This potential situation could result in unsafe { mutex.offset_from(&rust_mutex_pool[0] as *const _) } being operating on a null pointer, I guess it might trigger undefined behavior (UB). For safety reasons, I felt it necessary to report this issue. If you have performed checks elsewhere that ensure this is safe, please don’t take offense at my raising this issue.
I suggest Several possible fixes:

  1. If there is no external usage for free_mutex, it should not marked as pub.
  2. free_mutex method should add additional check for null pointer.
  3. mark free_mutex method as unsafe and proper doc to let users know that they should provide valid Pointers.
@lwz23
Copy link
Author

lwz23 commented Dec 16, 2024

ping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant