All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	kuniyu@amazon.com, dsahern@kernel.org, horms@kernel.org,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+3f18ef0f7df107a3f6a0@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next] inet: fix lwtunnel_valid_encap_type() lock imbalance
Date: Thu, 06 Mar 2025 03:30:34 +0000	[thread overview]
Message-ID: <174123183424.1114452.760275294340733893.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304125918.2763514-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  4 Mar 2025 12:59:18 +0000 you wrote:
> After blamed commit rtm_to_fib_config() now calls
> lwtunnel_valid_encap_type{_attr}() without RTNL held,
> triggering an unlock balance in __rtnl_unlock,
> as reported by syzbot [1]
> 
> IPv6 and rtm_to_nh_config() are not yet converted.
> 
> [...]

Here is the summary with links:
  - [net-next] inet: fix lwtunnel_valid_encap_type() lock imbalance
    https://git.kernel.org/netdev/net-next/c/f130a0cc1b4f

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



      parent reply	other threads:[~2025-03-06  3:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 12:59 [PATCH net-next] inet: fix lwtunnel_valid_encap_type() lock imbalance Eric Dumazet
2025-03-04 18:44 ` Kuniyuki Iwashima
2025-03-06  3:30 ` 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=174123183424.1114452.760275294340733893.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+3f18ef0f7df107a3f6a0@syzkaller.appspotmail.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.