On Fri, Jul 1, 2022 at 6:22 AM Daniel Borkmann <daniel@xxxxxxxxxxxxx> wrote: > > On 7/1/22 2:16 AM, Stanislav Fomichev wrote: > > On Thu, Jun 30, 2022 at 4:48 PM Hao Luo <haoluo@xxxxxxxxxx> wrote: > >> On Thu, Jun 30, 2022 at 3:42 PM Stanislav Fomichev <sdf@xxxxxxxxxx> wrote: [...] > >> > >> It seems ENOTSUPP is only used in the kernel. I wonder whether we > >> should let libbpf map ENOTSUPP to ENOTSUP, which is the errno used in > >> userspace and has been used in libbpf. > > > > Yeah, this comes up occasionally, I don't think we've agreed on some > > kind of general policy about what to do with these :-( > > Thanks for the review! > > Consensus was that for existing code, the ship has sailed to change it given > applications could one way or another depend on this error code, but it should > be avoided for new APIs (e.g. [0]). > > Thanks, > Daniel > > [0] https://lore.kernel.org/bpf/20211209182349.038ac2b8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ Thanks for the reference!
