The AT_EMPTY_PATH missing definition bug was fixed, which renders this bug (IMO) invalid, as the answer to "those headers conflict" is "then don't include both", which is often true of kernel and userspace headers with similar names.
The AT_EMPTY_PATH missing definition bug was fixed, which renders this bug (IMO) invalid, as the answer to "those headers conflict" is "then don't include both", which is often true of kernel and userspace headers with similar names.