Re: [PATCHv3 bpf 0/3] Fix pining maps after reuse map fd

Hello: This series was applied to bpf/bpf-next.git (refs/heads/master): On Tue, 6 Oct 2020 10:13:42 +0800 you wrote: > When a user reuse map fd after creating a map manually and set the > pin_path, then load the object via libbpf. bpf_object__create_maps() > will skip pinning map if map fd exist

Re: [PATCH bpf-next v2 1/2] samples/bpf: change Makefile to cope with latest llvm

Hello: This series was applied to bpf/bpf-next.git (refs/heads/master): On Mon, 5 Oct 2020 21:34:26 -0700 you wrote: > With latest llvm trunk, bpf programs under samples/bpf > directory, if using CORE, may experience the following > errors: > > LLVM ERROR: Cannot select: intrinsic %llvm.preserve

Re: [PATCH bpf-next 1/3] samples: bpf: split xdpsock stats into new struct

Hello: This series was applied to bpf/bpf-next.git (refs/heads/master): On Fri, 2 Oct 2020 13:36:10 + you wrote: > New statistics will be added in future commits. In preparation for this, > let's split out the existing statistics into their own struct. > > Signed-off-by: Ciara Loftus > ---

Re: [PATCH v3] selftests/bpf: Fix test_verifier after introducing resolve_pseudo_ldimm64

Hello: This patch was applied to bpf/bpf-next.git (refs/heads/master): On Tue, 6 Oct 2020 19:28:57 -0700 you wrote: > Commit 4976b718c355 ("bpf: Introduce pseudo_btf_id") switched > the order of check_subprogs() and resolve_pseudo_ldimm() in > the verifier. Now an empty prog expects to see the e