BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements
Date: Tue, 19 Jul 2022 16:50:15 +0000	[thread overview]
Message-ID: <165824941568.16633.17775134783985730826.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220715053146.1291891-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 14 Jul 2022 22:31:42 -0700 you wrote:
> Fix 32-bit overflow in value pointer calculations in BPF array map. And then
> raise obsolete limit on array map value size. Add selftest making sure this is
> working as intended.
> 
> v1->v2:
>   - fix broken patch #1 (no mask_index use in helper, as stated in commit
>     message; and add missing semicolon).
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/4] bpf: fix potential 32-bit overflow when accessing ARRAY map element
    https://git.kernel.org/bpf/bpf-next/c/87ac0d600943
  - [v2,bpf-next,2/4] bpf: make uniform use of array->elem_size everywhere in arraymap.c
    https://git.kernel.org/bpf/bpf-next/c/d937bc3449fa
  - [v2,bpf-next,3/4] bpf: remove obsolete KMALLOC_MAX_SIZE restriction on array map value size
    https://git.kernel.org/bpf/bpf-next/c/63b8ce77b15e
  - [v2,bpf-next,4/4] selftests/bpf: validate .bss section bigger than 8MB is possible now
    https://git.kernel.org/bpf/bpf-next/c/243164612005

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



      parent reply	other threads:[~2022-07-19 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15  5:31 [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements Andrii Nakryiko
2022-07-15  5:31 ` [PATCH v2 bpf-next 1/4] bpf: fix potential 32-bit overflow when accessing ARRAY map element Andrii Nakryiko
2022-07-15  5:31 ` [PATCH v2 bpf-next 2/4] bpf: make uniform use of array->elem_size everywhere in arraymap.c Andrii Nakryiko
2022-07-15  5:31 ` [PATCH v2 bpf-next 3/4] bpf: remove obsolete KMALLOC_MAX_SIZE restriction on array map value size Andrii Nakryiko
2022-07-15  5:31 ` [PATCH v2 bpf-next 4/4] selftests/bpf: validate .bss section bigger than 8MB is possible now Andrii Nakryiko
2022-07-15 16:29 ` [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements Yonghong Song
2022-07-19 16:50 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=165824941568.16633.17775134783985730826.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox