All of lore.kernel.org
 help / color / mirror / Atom feed
From: Menglong Dong <menglong.dong@linux.dev>
To: Fushuai Wang <wangfushuai@baidu.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, ast@kernel.org,
	martin.lau@kernel.org, houtao1@huawei.com, jkangas@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Fushuai Wang <wangfushuai@baidu.com>,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Use rcu_read_lock_dont_migrate() and and rcu_read_unlock_migrate()
Date: Tue, 07 Oct 2025 11:49:42 +0800	[thread overview]
Message-ID: <3379803.44csPzL39Z@7950hx> (raw)
In-Reply-To: <20251005150816.38799-1-wangfushuai@baidu.com>

On 2025/10/5 23:08, Fushuai Wang wrote:
> Replace the combination of migrate_disable()/migrate_enable() and rcu_read_lock()/rcu_read_unlock()
> with rcu_read_lock_dont_migrate()/rcu_read_unlock_migrate() in bpf_sk_storage.c.

Hi, Fushuai. There are some nits in you patch:

1. The title is too fuzzy. It can be
    "bpf: Use rcu_read_lock_dont_migrate in bpf_sk_storage.c"
2. You can wrap the commit log and don't exceed 75 character per line.
    This is not necessary, but it can stop the check_patch from
    complaining.

And I think you shoud CC bpf@vger.kernel.org too. Before you
send the patch, you can check it with ./scripts/checkpatch.pl to
find potential problems.

Thanks!
Menglong Dong

> 
> Signed-off-by: Fushuai Wang <wangfushuai@baidu.com>
> ---
>  net/core/bpf_sk_storage.c | 12 ++++--------
>  1 file changed, 4 insertions(+), 8 deletions(-)
> 
> diff --git a/net/core/bpf_sk_storage.c b/net/core/bpf_sk_storage.c
> index 2e538399757f..bdb70cf89ae1 100644
> --- a/net/core/bpf_sk_storage.c
> +++ b/net/core/bpf_sk_storage.c
> @@ -50,16 +50,14 @@ void bpf_sk_storage_free(struct sock *sk)
>  {
>  	struct bpf_local_storage *sk_storage;
>  
> -	migrate_disable();
> -	rcu_read_lock();
> +	rcu_read_lock_dont_migrate();
>  	sk_storage = rcu_dereference(sk->sk_bpf_storage);
>  	if (!sk_storage)
>  		goto out;
>  
>  	bpf_local_storage_destroy(sk_storage);
>  out:
> -	rcu_read_unlock();
> -	migrate_enable();
> +	rcu_read_unlock_migrate();
>  }
>  
>  static void bpf_sk_storage_map_free(struct bpf_map *map)
> @@ -161,8 +159,7 @@ int bpf_sk_storage_clone(const struct sock *sk, struct sock *newsk)
>  
>  	RCU_INIT_POINTER(newsk->sk_bpf_storage, NULL);
>  
> -	migrate_disable();
> -	rcu_read_lock();
> +	rcu_read_lock_dont_migrate();
>  	sk_storage = rcu_dereference(sk->sk_bpf_storage);
>  
>  	if (!sk_storage || hlist_empty(&sk_storage->list))
> @@ -213,9 +210,8 @@ int bpf_sk_storage_clone(const struct sock *sk, struct sock *newsk)
>  	}
>  
>  out:
> -	rcu_read_unlock();
> -	migrate_enable();
>  
> +	rcu_read_unlock_migrate();
>  	/* In case of an error, don't free anything explicitly here, the
>  	 * caller is responsible to call bpf_sk_storage_free.
>  	 */
> 





      reply	other threads:[~2025-10-07  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 15:08 [PATCH bpf-next] bpf: Use rcu_read_lock_dont_migrate() and and rcu_read_unlock_migrate() Fushuai Wang
2025-10-07  3:49 ` Menglong Dong [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=3379803.44csPzL39Z@7950hx \
    --to=menglong.dong@linux.dev \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=jkangas@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wangfushuai@baidu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.