From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, skalluru@marvell.com, manishc@marvell.com,
andrew+netdev@lunn.ch, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
tariqt@nvidia.com, saeedm@nvidia.com, louis.peens@corigine.com,
shshaikh@marvell.com, GR-Linux-NIC-Dev@marvell.com,
ecree.xilinx@gmail.com, horms@kernel.org, dsahern@kernel.org,
shuah@kernel.org, mheib@redhat.com, ruanjinjie@huawei.com,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, oss-drivers@corigine.com,
linux-net-drivers@amd.com, linux-kselftest@vger.kernel.org,
leon@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 0/4] udp_tunnel: remove rtnl_lock dependency
Date: Mon, 9 Jun 2025 15:38:17 -0700 [thread overview]
Message-ID: <20250609153817.14d7e762@kernel.org> (raw)
In-Reply-To: <20250609162541.1230022-1-stfomichev@gmail.com>
On Mon, 9 Jun 2025 09:25:37 -0700 Stanislav Fomichev wrote:
> Recently bnxt had to grow back a bunch of rtnl dependencies because
> of udp_tunnel's infra. Add separate (global) mutext to protect
> udp_tunnel state.
Appears to break the selftest, unfortunately:
https://netdev.bots.linux.dev/contest.html?test=udp-tunnel-nic-sh&branch=net-next-2025-06-09--21-00
--
pw-bot: cr
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, skalluru@marvell.com, manishc@marvell.com,
andrew+netdev@lunn.ch, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
tariqt@nvidia.com, saeedm@nvidia.com, louis.peens@corigine.com,
shshaikh@marvell.com, GR-Linux-NIC-Dev@marvell.com,
ecree.xilinx@gmail.com, horms@kernel.org, dsahern@kernel.org,
shuah@kernel.org, mheib@redhat.com, ruanjinjie@huawei.com,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, oss-drivers@corigine.com,
linux-net-drivers@amd.com, linux-kselftest@vger.kernel.org,
leon@kernel.org
Subject: Re: [PATCH net-next v2 0/4] udp_tunnel: remove rtnl_lock dependency
Date: Mon, 9 Jun 2025 15:38:17 -0700 [thread overview]
Message-ID: <20250609153817.14d7e762@kernel.org> (raw)
In-Reply-To: <20250609162541.1230022-1-stfomichev@gmail.com>
On Mon, 9 Jun 2025 09:25:37 -0700 Stanislav Fomichev wrote:
> Recently bnxt had to grow back a bunch of rtnl dependencies because
> of udp_tunnel's infra. Add separate (global) mutext to protect
> udp_tunnel state.
Appears to break the selftest, unfortunately:
https://netdev.bots.linux.dev/contest.html?test=udp-tunnel-nic-sh&branch=net-next-2025-06-09--21-00
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-09 22:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 16:25 [Intel-wired-lan] [PATCH net-next v2 0/4] udp_tunnel: remove rtnl_lock dependency Stanislav Fomichev
2025-06-09 16:25 ` Stanislav Fomichev
2025-06-09 16:25 ` [Intel-wired-lan] [PATCH net-next v2 1/4] " Stanislav Fomichev
2025-06-09 16:25 ` Stanislav Fomichev
2025-06-10 14:57 ` [Intel-wired-lan] " Cosmin Ratiu
2025-06-10 14:57 ` Cosmin Ratiu
2025-06-09 16:25 ` [Intel-wired-lan] [PATCH net-next v2 2/4] net: remove redundant ASSERT_RTNL() in queue setup functions Stanislav Fomichev
2025-06-09 16:25 ` Stanislav Fomichev
2025-06-09 16:25 ` [Intel-wired-lan] [PATCH net-next v2 3/4] netdevsim: remove udp_ports_sleep Stanislav Fomichev
2025-06-09 16:25 ` Stanislav Fomichev
2025-06-09 18:56 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-09 18:56 ` Loktionov, Aleksandr
2025-06-09 16:25 ` [Intel-wired-lan] [PATCH net-next v2 4/4] Revert "bnxt_en: bring back rtnl_lock() in the bnxt_open() path" Stanislav Fomichev
2025-06-09 16:25 ` Stanislav Fomichev
2025-06-09 22:38 ` Jakub Kicinski [this message]
2025-06-09 22:38 ` [PATCH net-next v2 0/4] udp_tunnel: remove rtnl_lock dependency Jakub Kicinski
2025-06-09 23:19 ` [Intel-wired-lan] " Stanislav Fomichev
2025-06-09 23:19 ` Stanislav Fomichev
2025-06-09 23:28 ` [Intel-wired-lan] " Jakub Kicinski
2025-06-09 23:28 ` Jakub Kicinski
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=20250609153817.14d7e762@kernel.org \
--to=kuba@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=linux-rdma@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=manishc@marvell.com \
--cc=mheib@redhat.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=ruanjinjie@huawei.com \
--cc=saeedm@nvidia.com \
--cc=shshaikh@marvell.com \
--cc=shuah@kernel.org \
--cc=skalluru@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.com \
--cc=stfomichev@gmail.com \
--cc=tariqt@nvidia.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.