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

Program information returned from extensions should be strongly typed #82

Closed
poornagmsft opened this issue Apr 25, 2021 · 2 comments · Fixed by #302
Closed

Program information returned from extensions should be strongly typed #82

poornagmsft opened this issue Apr 25, 2021 · 2 comments · Fixed by #302
Assignees
Labels
ebpf-km PR/Issues for kernel mode components triaged Discussed in a triage meeting
Milestone

Comments

@poornagmsft
Copy link
Contributor

@shankarseal

@poornagmsft poornagmsft added the ebpf-km PR/Issues for kernel mode components label Apr 25, 2021
@poornagmsft poornagmsft added this to the 2107 milestone Apr 25, 2021
@Alan-Jowett Alan-Jowett changed the title Program info for verifier and jitter to query context and program type specific helpers Program information returned from extensions should be strongly typed May 5, 2021
@dthaler dthaler added triaged Discussed in a triage meeting and removed triaged Discussed in a triage meeting labels Jun 7, 2021
@dthaler
Copy link
Collaborator

dthaler commented Jun 7, 2021

@Alan-Jowett please add description as discussed in triage meeting

@Alan-Jowett
Copy link
Member

The contract between extension and EbpfCore.sys is to pass the program type information as an opaque blob that is interpreted by the eBPF service.

The ask is to pass this as a strongly typed pointer and have EbpfCore.sys serialize the program type information.

@dthaler dthaler added the triaged Discussed in a triage meeting label Jun 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ebpf-km PR/Issues for kernel mode components triaged Discussed in a triage meeting
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants