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

Draft STPA for stack protection #4

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

reiterative
Copy link
Collaborator

No description provided.

@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch from 2c6b49e to 682524d Compare November 17, 2021 17:33
@reiterative
Copy link
Collaborator Author

@coppermanME Thanks for the input, Elana! Sorry that I forgot to include a link to this PR - please can you add your comments here instead of in the files?

@coppermanME
Copy link

[EC] Why only stack overflow issues?
[EC] Why only data protection? Code may also be corrupted by stack overflow.

[EC] Why is stack depth overflow a concern only for kernel data structures, whereas stack overflow is a concern only for application data?

[EC] Assets to be protected are data and code, in kernel and user space.

@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch from 9450aaa to 682524d Compare November 17, 2021 21:08
@reiterative
Copy link
Collaborator Author

[EC] Why only stack overflow issues?

This was just a quick initial draft. Very happy to add other hazards related to the stack!

[EC] Why only data protection? Code may also be corrupted by stack overflow.

OK. I'll add that.

[EC] Why is stack depth overflow a concern only for kernel data structures, whereas stack overflow is a concern only for application data?

I was reading about stack depth overflow in the kernel context, and hadn't made the logical connection that it might apply in userspace too.

[EC] Assets to be protected are data and code, in kernel and user space.

Will update.

@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch 4 times, most recently from fc80746 to 7172f4f Compare December 14, 2021 14:14
@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch 4 times, most recently from 547597b to dc750b6 Compare January 13, 2022 11:27
@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch from 421da5e to dfdf709 Compare January 13, 2022 13:51
@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch 2 times, most recently from 986e7e3 to 75d63de Compare January 26, 2022 16:39
Signed-off-by: Paul Albertella <[email protected]>
* Add assumptions to README
* Rewrite losses, hazards and constraints

Signed-off-by: Paul Albertella <[email protected]>
Signed-off-by: Paul Albertella <[email protected]>
Signed-off-by: Paul Albertella <[email protected]>
Signed-off-by: Paul Albertella <[email protected]>
* Rename 'Scehduler' to avoid confusion

Signed-off-by: Paul Albertella <[email protected]>
Signed-off-by: Paul Albertella <[email protected]>
- Add feedback
- Compiler CA applies to all comnponents
- Hardware is not only interrupt source
- Cosmetic improvements

Signed-off-by: Paul Albertella <[email protected]>
* For system components only at this stage

Signed-off-by: Paul Albertella <[email protected]>
* Add call stack as a controller
* Remove subroutine controllers

Signed-off-by: Paul Albertella <[email protected]>
Signed-off-by: Paul Albertella <[email protected]>
@reiterative reiterative force-pushed the reiterative/stack-memory-stpa branch from 75d63de to e9aed40 Compare March 1, 2023 22:58
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

Successfully merging this pull request may close these issues.

2 participants