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

2020-10-06 Thread patchwork-bot+bpf 
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. Fix it by add moving bpf creation
> to else condition and go on checking map pin_path after that.
> 
> v3:
> for selftest: use CHECK() for bpf_object__open_file() and close map fd on 
> error
> 
> [...]

Here is the summary with links:
  - [PATCHv3,1/3] libbpf: close map fd if init map slots failed
https://git.kernel.org/bpf/bpf-next/c/a0f2b7acb4b1
  - [PATCHv3,2/3] libbpf: check if pin_path was set even map fd exist
https://git.kernel.org/bpf/bpf-next/c/2c193d32caee
  - [PATCHv3,3/3] selftest/bpf: test pinning map with reused map fd
https://git.kernel.org/bpf/bpf-next/c/44c4aa2bd151

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

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

2020-10-06 Thread patchwork-bot+bpf 
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.struct.access.index
> PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash 
> backtrace.
> Stack dump:
> 0.  Program arguments: llc -march=bpf -filetype=obj -o 
> samples/bpf/test_probe_write_user_kern.o
> 1.  Running pass 'Function Pass Manager' on module ''.
> 2.  Running pass 'BPF DAG->DAG Pattern Instruction Selection' on function 
> '@bpf_prog1'
>  #0 0x0183c26c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
> 
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x183c26c)
> ...
>  #7 0x017c375e 
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x17c375e)
>  #8 0x016a75c5 llvm::SelectionDAGISel::CannotYetSelect(llvm::SDNode*)
> 
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x16a75c5)
>  #9 0x016ab4f8 
> llvm::SelectionDAGISel::SelectCodeCommon(llvm::SDNode*, unsigned char const*,
> unsigned int) 
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x16ab4f8)
> ...
> Aborted (core dumped) | llc -march=bpf -filetype=obj -o 
> samples/bpf/test_probe_write_user_kern.o
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] samples/bpf: change Makefile to cope with latest llvm
https://git.kernel.org/bpf/bpf-next/c/9618bde489b2
  - [bpf-next,v2,2/2] samples/bpf: fix a compilation error with fallthrough 
marking
https://git.kernel.org/bpf/bpf-next/c/544d6adf3c3d

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

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

2020-10-06 Thread patchwork-bot+bpf 
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 
> ---
>  samples/bpf/xdpsock_user.c | 123 +
>  1 file changed, 69 insertions(+), 54 deletions(-)

Here is the summary with links:
  - [bpf-next,1/3] samples: bpf: split xdpsock stats into new struct
https://git.kernel.org/bpf/bpf-next/c/2e8806f032f5
  - [bpf-next,2/3] samples: bpf: count syscalls in xdpsock
https://git.kernel.org/bpf/bpf-next/c/60dc609dbd54
  - [bpf-next,3/3] samples: bpf: driver interrupt statistics in xdpsock
https://git.kernel.org/bpf/bpf-next/c/67ed375530e2

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

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

2020-10-06 Thread patchwork-bot+bpf 
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 error "last
> insn is not an the prog of a single invalid ldimm exit or jmp"
> instead, because the check for subprogs comes first. It's now
> pointless to validate that half of ldimm64 won't be the last
> instruction.
> 
> [...]

Here is the summary with links:
  - [v3] selftests/bpf: Fix test_verifier after introducing 
resolve_pseudo_ldimm64
https://git.kernel.org/bpf/bpf-next/c/bf88a80a0407

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html