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

Address access sanitation #22

Open
kvark opened this issue Aug 10, 2017 · 2 comments
Open

Address access sanitation #22

kvark opened this issue Aug 10, 2017 · 2 comments

Comments

@kvark
Copy link
Member

kvark commented Aug 10, 2017

We need a way of modifying the SPIR-V so that no resource access goes beyond the bounds, for the sake of GPUWeb security. Some of the checks could be omitted by doing a static analysis, but a general approach could be injecting the code that queries buffers/images dimensions and reset the address offset to 0 using a dynamic check for that address to be in the bounds.

@kvark
Copy link
Member Author

kvark commented Oct 11, 2017

@dneto0's experimental code in SPIRV-Tools: https://github.com/dneto0/SPIRV-Tools/tree/robust-access

@antiagainst
Copy link
Collaborator

Cool! I'll take a look and find some time to working on rspirv.

Been quite absorbed by SPIR-V CodeGen in DirectXShaderCompiler recently. :)

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

2 participants