Skip to content

reconsider k_mbox APIs #3759

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.

Sign up for GitHub

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

Jump to bottom
Closed
zephyrbot opened this issue Jun 28, 2017 · 0 comments
Closed

reconsider k_mbox APIs #3759

zephyrbot opened this issue Jun 28, 2017 · 0 comments
Labels
area: API Changes to public APIs area: Kernel Enhancement Changes/Updates/Additions to existing features

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Jun 28, 2017 •
edited
Loading

Reported by Andrew Boie:

The current design of the k_mbox APIs involves struct k_mbox_msg data structures which are intended to be instantiated and populated by the user. Corruption of these data structures could crash the kernel. We need a bulletproof way to sanitize these structures, or make some API changes, or decide that k_mbox APIs will be supervisor-only.

(Imported from Jira ZEP-2325)
@zephyrbot zephyrbot added area: Kernel Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
@zephyrbot zephyrbot added this to the v1.11.0 milestone Sep 23, 2017
@zephyrbot zephyrbot mentioned this issue Sep 23, 2017
Closed
39 tasks
@carlescufi carlescufi modified the milestones: v1.11.0, v1.12.0 Mar 9, 2018
@nashif nashif removed this from the v1.12.0 milestone Sep 5, 2018
@galak galak added the area: API Changes to public APIs label Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: API Changes to public APIs area: Kernel Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nashif @andrewboie @carlescufi @galak @zephyrbot