mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <a.kovaleva@yadro.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>,
	<johannes@sipsolutions.net>, <kuba@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux@yadro.com>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>,
	<stable@vger.kernel.org>, <kuniyu@amazon.com>
Subject: Re: [PATCH v3 net] net: Fix an unsafe loop on the list
Date: Thu, 3 Oct 2024 15:16:07 -0700	[thread overview]
Message-ID: <20241003221607.13408-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20241003104431.12391-1-a.kovaleva@yadro.com>

From: Anastasia Kovaleva <a.kovaleva@yadro.com>
Date: Thu, 3 Oct 2024 13:44:31 +0300
> The kernel may crash when deleting a genetlink family if there are still
> listeners for that family:
> 
> Oops: Kernel access of bad area, sig: 11 [#1]
>   ...
>   NIP [c000000000c080bc] netlink_update_socket_mc+0x3c/0xc0
>   LR [c000000000c0f764] __netlink_clear_multicast_users+0x74/0xc0
>   Call Trace:
> __netlink_clear_multicast_users+0x74/0xc0
> genl_unregister_family+0xd4/0x2d0
> 
> Change the unsafe loop on the list to a safe one, because inside the
> loop there is an element removal from this list.
> 
> Fixes: b8273570f802 ("genetlink: fix netns vs. netlink table locking (2)")
> Cc: stable@vger.kernel.org
> Signed-off-by: Anastasia Kovaleva <a.kovaleva@yadro.com>
> Reviewed-by: Dmitry Bogdanov <d.bogdanov@yadro.com>

Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>


> ---
> v3: remove trailing "\", change spaces to tab
> v2: add CC tag for stable
> ---
>  include/net/sock.h       | 2 ++
>  net/netlink/af_netlink.c | 3 ++-
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/include/net/sock.h b/include/net/sock.h
> index c58ca8dd561b..db29c39e19a7 100644
> --- a/include/net/sock.h
> +++ b/include/net/sock.h
> @@ -894,6 +894,8 @@ static inline void sk_add_bind_node(struct sock *sk,
>  	hlist_for_each_entry_safe(__sk, tmp, list, sk_node)
>  #define sk_for_each_bound(__sk, list) \
>  	hlist_for_each_entry(__sk, list, sk_bind_node)
> +#define sk_for_each_bound_safe(__sk, tmp, list) \
> +	hlist_for_each_entry_safe(__sk, tmp, list, sk_bind_node)
>  
>  /**
>   * sk_for_each_entry_offset_rcu - iterate over a list at a given struct offset
> diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
> index 0b7a89db3ab7..0a9287fadb47 100644
> --- a/net/netlink/af_netlink.c
> +++ b/net/netlink/af_netlink.c
> @@ -2136,8 +2136,9 @@ void __netlink_clear_multicast_users(struct sock *ksk, unsigned int group)
>  {
>  	struct sock *sk;
>  	struct netlink_table *tbl = &nl_table[ksk->sk_protocol];
> +	struct hlist_node *tmp;
>  
> -	sk_for_each_bound(sk, &tbl->mc_list)
> +	sk_for_each_bound_safe(sk, tmp, &tbl->mc_list)
>  		netlink_update_socket_mc(nlk_sk(sk), group, 0);
>  }
>  
> -- 
> 2.40.1

  reply	other threads:[~2024-10-03 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 10:44 Anastasia Kovaleva
2024-10-03 22:16 ` Kuniyuki Iwashima [this message]
2024-10-04 23:00 ` patchwork-bot+netdevbpf

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=20241003221607.13408-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=a.kovaleva@yadro.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@yadro.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®