lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 9 Sep 2022 15:48:29 +0200 From: Jesper Dangaard Brouer <jbrouer@...hat.com> To: Alexander Lobakin <alexandr.lobakin@...el.com> Cc: brouer@...hat.com, bpf@...r.kernel.org, netdev@...r.kernel.org, xdp-hints@...-project.net, larysa.zaremba@...el.com, memxor@...il.com, Lorenzo Bianconi <lorenzo@...nel.org>, mtahhan@...hat.com, Alexei Starovoitov <alexei.starovoitov@...il.com>, Daniel Borkmann <borkmann@...earbox.net>, Andrii Nakryiko <andrii.nakryiko@...il.com>, dave@...cker.co.uk, Magnus Karlsson <magnus.karlsson@...el.com>, bjorn@...nel.org Subject: Re: [xdp-hints] [PATCH RFCv2 bpf-next 00/18] XDP-hints: XDP gaining access to HW offload hints via BTF On 08/09/2022 11.30, Alexander Lobakin wrote: > From: Jesper Dangaard Brouer <brouer@...hat.com> > Date: Wed, 07 Sep 2022 17:45:00 +0200 > >> This patchset expose the traditional hardware offload hints to XDP and >> rely on BTF to expose the layout to users. >> [...] >> The main different from RFC-v1: >> - Drop idea of BTF "origin" (vmlinux, module or local) >> - Instead to use full 64-bit BTF ID that combine object+type ID >> >> I've taken some of Alexandr/Larysa's libbpf patches and integrated >> those. > > Not sure if it's okay to inform the authors about the fact only > after sending? Esp from the eeeh... "incompatible" implementation? Just to be clear: I have made sure that developers of the patches maintain authorship (when applied to git via the From: line) and I've Cc'ed the developers directly. I didn't Cc you directly as I knew you would be included via XDP-hints list, and I didn't directly use one of your patches. > I realize it's open code, but this looks sorta depreciatingly. After discussions with Larysa on pre-patchset, I was convinced of the idea of a full 64-bit BTF ID. Thus, I took those patches and carried them in my patchset, instead of reimplementing the same myself. Precisely out of respect for Larysa's work as I wanted to give her credit for coding this. I'm very interested in collaborating. That is why I have picked up patches from your patchset and are carrying them forward. I could just as easily reimplemented them myself. --Jesper
Powered by blists - more mailing lists