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.

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

Security Monitor (2) #200

Merged
merged 6 commits into from
Aug 21, 2024
Merged

Security Monitor (2) #200

merged 6 commits into from
Aug 21, 2024

Conversation

dbittman
Copy link
Contributor

This PR is the second in a series implementing the security monitor, building off #199. It implements:

  • Mapping objects using the new monitor implementation.
  • Spawning compartment threads.
  • Getting compartment config info.
  • Implements Monitor struct locking.
  • Monitor init up till ready to load a compartment (next PR :) )

@dbittman dbittman added the enhancement New feature or request label Aug 15, 2024
@dbittman dbittman self-assigned this Aug 15, 2024
Base automatically changed from dbittman-monitor2 to main August 20, 2024 23:30
@dbittman dbittman marked this pull request as ready for review August 21, 2024 01:02
@dbittman dbittman requested a review from gvnn3 as a code owner August 21, 2024 01:02
gvnn3
gvnn3 approved these changes Aug 21, 2024
View reviewed changes
Copy link
Contributor

@gvnn3 gvnn3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this in as well.

@dbittman dbittman merged commit 5df86c4 into main Aug 21, 2024
1 check passed
@dbittman dbittman deleted the dbittman-monitor3 branch August 21, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gvnn3 gvnn3 gvnn3 approved these changes

Assignees

@dbittman dbittman

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dbittman @gvnn3