You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you please specify the license explicitly in the pf_ring.h file?
The absence of explicit declaration creates ambiguity when linking with the user-space pfring library.
The library itself is distributed under LGPLv2.1. But the pfring.h header file includes a linux/pf_ring.h file, which refers to a kernel module distributed under the GPLv2 license.
And it turns out that the code that links with the user-space pfring library implicitly uses header files under the GPLv2 license. It can be a significant issue under certain circumstances, because the position of the GPLv2 is that generally, using GPLv2 code in a work makes the whole work subject to the GPLv2.
The text was updated successfully, but these errors were encountered:
The pf_ring.h header file part of the kernel module (GPLv2) is included by the userspace library (LGPLv2.1) to access the socket API (data structures). How are you suggesting to change the header files in practice?
In practice I would like to see something like license exception which exists in Linux kernel for User-space API (UAPI) header files. There is an explicit syscall exception described in LICENSES/exceptions/Linux-syscall-note (https://github.com/torvalds/linux/blob/master/LICENSES/exceptions/Linux-syscall-note), which does not extend the GPLv2 requirements to any software which uses it to communicate with the kernel.
So just the reference to Linux-syscall-note would be fine.
Could you please specify the license explicitly in the pf_ring.h file?
The absence of explicit declaration creates ambiguity when linking with the user-space pfring library.
The library itself is distributed under LGPLv2.1. But the pfring.h header file includes a linux/pf_ring.h file, which refers to a kernel module distributed under the GPLv2 license.
And it turns out that the code that links with the user-space pfring library implicitly uses header files under the GPLv2 license. It can be a significant issue under certain circumstances, because the position of the GPLv2 is that generally, using GPLv2 code in a work makes the whole work subject to the GPLv2.
The text was updated successfully, but these errors were encountered: