Skip to content

Device Driver Access Control #3635

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

Closed
zephyrbot opened this issue May 25, 2017 · 2 comments
Closed

Device Driver Access Control #3635

zephyrbot opened this issue May 25, 2017 · 2 comments
Assignees
Labels
area: Kernel Enhancement Changes/Updates/Additions to existing features priority: medium Medium impact/importance bug
Milestone

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented May 25, 2017

Reported by Andrew Boie:

For memory protection we want to selectively grant threads access to device driver APIs, all-or-nothing may be too coarse for security concerns. However, it may not be feasible to implement this on all arches, as some MPU-based systems may have too few available regions to do this properly. Design an optional access control mechanism and APIs such that a thread can designate what drivers or subsystems it has access to before it drops supervisor privileges.

(Imported from Jira ZEP-2197)

@zephyrbot
Copy link
Collaborator Author

by Andrew Boie:

The current plan is to treat instances of struct device just like any other kernel object, using the same mechanism for permission tracking. So I think this JIRA may be a no-op.

@zephyrbot
Copy link
Collaborator Author

by Andrew Boie:

Same mechanism as kernel object access control.

@zephyrbot zephyrbot added priority: medium Medium impact/importance bug area: Kernel Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
@zephyrbot zephyrbot added this to the v1.10.0 milestone Sep 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Kernel Enhancement Changes/Updates/Additions to existing features priority: medium Medium impact/importance bug
Projects
None yet
Development

No branches or pull requests

2 participants