BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
	alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
	haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
	john.fastabend@gmail.com, paulmck@kernel.org, houtao1@huawei.com
Subject: Re: [PATCH bpf v5 0/7] bpf: Fix the release of inner map
Date: Tue, 05 Dec 2023 02:08:19 +0000	[thread overview]
Message-ID: <170174209904.18867.7610457582102890894.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231204140425.1480317-1-houtao@huaweicloud.com>

Hello:

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

On Mon,  4 Dec 2023 22:04:18 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The patchset aims to fix the release of inner map in map array or map
> htab. The release of inner map is different with normal map. For normal
> map, the map is released after the bpf program which uses the map is
> destroyed, because the bpf program tracks the used maps. However bpf
> program can not track the used inner map because these inner map may be
> updated or deleted dynamically, and for now the ref-counter of inner map
> is decreased after the inner map is remove from outer map, so the inner
> map may be freed before the bpf program, which is accessing the inner
> map, exits and there will be use-after-free problem as demonstrated by
> patch #6.
> 
> [...]

Here is the summary with links:
  - [bpf,v5,1/7] bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    https://git.kernel.org/bpf/bpf-next/c/169410eba271
  - [bpf,v5,2/7] bpf: Add map and need_defer parameters to .map_fd_put_ptr()
    https://git.kernel.org/bpf/bpf-next/c/20c20bd11a07
  - [bpf,v5,3/7] bpf: Set need_defer as false when clearing fd array during map free
    https://git.kernel.org/bpf/bpf-next/c/79d93b3c6ffd
  - [bpf,v5,4/7] bpf: Defer the free of inner map when necessary
    https://git.kernel.org/bpf/bpf-next/c/876673364161
  - [bpf,v5,5/7] bpf: Optimize the free of inner map
    https://git.kernel.org/bpf/bpf-next/c/af66bfd3c853
  - [bpf,v5,6/7] selftests/bpf: Add test cases for inner map
    https://git.kernel.org/bpf/bpf-next/c/1624918be84a
  - [bpf,v5,7/7] selftests/bpf: Test outer map update operations in syscall program
    https://git.kernel.org/bpf/bpf-next/c/e3dd40828534

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



      parent reply	other threads:[~2023-12-05  2:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 14:04 [PATCH bpf v5 0/7] bpf: Fix the release of inner map Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 1/7] bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 2/7] bpf: Add map and need_defer parameters to .map_fd_put_ptr() Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 3/7] bpf: Set need_defer as false when clearing fd array during map free Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 4/7] bpf: Defer the free of inner map when necessary Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 5/7] bpf: Optimize the free of inner map Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 6/7] selftests/bpf: Add test cases for " Hou Tao
2023-12-04 14:04 ` [PATCH bpf v5 7/7] selftests/bpf: Test outer map update operations in syscall program Hou Tao
2023-12-05  2:08 ` 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=170174209904.18867.7610457582102890894.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=houtao1@huawei.com \
    --cc=houtao@huaweicloud.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=paulmck@kernel.org \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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