public inbox for bpf@vger.kernel.org
 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,
	eddyz87@gmail.com, song@kernel.org, haoluo@google.com,
	yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@fomichev.me, jolsa@kernel.org,
	john.fastabend@gmail.com, bigeasy@linutronix.de,
	houtao1@huawei.com, xukuohai@huawei.com
Subject: Re: [PATCH bpf-next 0/3] Fix lockdep warning for htab of map
Date: Fri, 08 Nov 2024 19:50:29 +0000	[thread overview]
Message-ID: <173109542975.2744281.12366813939147315544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241106063542.357743-1-houtao@huaweicloud.com>

Hello:

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

On Wed,  6 Nov 2024 14:35:39 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The patch set fixes a lockdep warning for htab of map. The
> warning is found when running test_maps. The warning occurs when
> htab_put_fd_value() attempts to acquire map_idr_lock to free the map id
> of the inner map while already holding the bucket lock (raw_spinlock_t).
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/3] bpf: Call free_htab_elem() after htab_unlock_bucket()
    https://git.kernel.org/bpf/bpf-next/c/81eef03cbf70
  - [bpf-next,2/3] selftests/bpf: Move ENOTSUPP from bpf_util.h
    https://git.kernel.org/bpf/bpf-next/c/7d5e83b4d41b
  - [bpf-next,3/3] selftests/bpf: Test the update operations for htab of maps
    https://git.kernel.org/bpf/bpf-next/c/ff605ec69735

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



      parent reply	other threads:[~2024-11-08 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  6:35 [PATCH bpf-next 0/3] Fix lockdep warning for htab of map Hou Tao
2024-11-06  6:35 ` [PATCH bpf-next 1/3] bpf: Call free_htab_elem() after htab_unlock_bucket() Hou Tao
2024-11-06  9:53   ` Hou Tao
2024-11-08 19:55     ` Alexei Starovoitov
2024-11-09  1:29       ` Hou Tao
2024-11-06  6:35 ` [PATCH bpf-next 2/3] selftests/bpf: Move ENOTSUPP from bpf_util.h Hou Tao
2024-11-06  6:35 ` [PATCH bpf-next 3/3] selftests/bpf: Test the update operations for htab of maps Hou Tao
2024-11-06  8:45 ` [PATCH bpf-next 0/3] Fix lockdep warning for htab of map Sebastian Andrzej Siewior
2024-11-06  9:48   ` Hou Tao
2024-11-06 10:05     ` Sebastian Andrzej Siewior
2024-11-08 19:52     ` Alexei Starovoitov
2024-11-09  1:48       ` Hou Tao
2024-11-09  1:55         ` Alexei Starovoitov
2024-11-08 19: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=173109542975.2744281.12366813939147315544.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --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=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=xukuohai@huawei.com \
    --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