-
Notifications
You must be signed in to change notification settings - Fork 234
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 PR - Differences between Fork & Official Repo #3627
base: main
Are you sure you want to change the base?
Conversation
Includes new hook entry function prototypes (flow_md_t and mac_md_t)
Current on stand-by waiting to see whether should continue using forked repo or new repo with submodule since the extension is not fully completed and code cannot be separated entirely from ebpf-for-windows. Thus, moving recent changed in ebpf-for-data-usage here.
Added the 2 basic eBPF programs
Defined program types, attach types, and callouts. Set up program info and data for registration, unregistration, for future hook work. Created skeleton for callout functions. Added generated program headers which contain encoded program info.
… fall back to using static data option for mac and flow program types.
Added program and hook prototypes
… Clang formatted it with the OS repo format (not the ebpf-for-windows clang-format). User mode app compiles and runs as expected.
…m into app_id_t struct which contains array to store app name. Made changes to console.cpp based on feedback
Added user mode application: console
…e with bpf_map_update_elem
Working hook callouts, five-tuple parsing, and UM app with upstream commits
Basic end-to-end tests
Create setup.md as instructions to building and running ebpf-for-data-usage
@trishms please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Description
Describe the purpose of and changes within this Pull Request.
Testing
Do any existing tests cover this change? Are new tests needed?
Documentation
Is there any documentation impact for this change?
Installation
Is there any installer impact for this change?