Skip to content

Conversation

@emanela
Copy link

@emanela emanela commented Oct 3, 2025

Description

device name wasn't set properly due to macro expansion behavior resulting in only one ebpf extension able to be loaded at a time.

Testing

Compiled extensions with the change and verified successful installation and running status for both extensions at the same time. I also verified via WinDbg that the device name set accordingly, e.g. \\device\\ebpf_ext_ntos and not \\device\\ebpf_ext_PROVIDER_NAME as before.

Documentation

No.

Installation

No.

device name wasn't set properly due to macro expansion behavior.

Signed-off-by: Elad Manela <elad.manela@upwind.io>
@emanela emanela force-pushed the ebpf_ext_device_name_fix branch from 91e9bb6 to a76580d Compare October 3, 2025 18:33
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.

1 participant