[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250311084507.3978048-1-sdf@fomichev.me>
Date: Tue, 11 Mar 2025 01:45:05 -0700
From: Stanislav Fomichev <sdf@...ichev.me>
To: netdev@...r.kernel.org
Cc: davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
linux-kernel@...r.kernel.org,
willemdebruijn.kernel@...il.com,
jasowang@...hat.com,
andrew+netdev@...n.ch,
horms@...nel.org,
sdf@...ichev.me,
jdamato@...tly.com,
kory.maincent@...tlin.com,
atenart@...nel.org,
kuniyu@...zon.com
Subject: [PATCH net-next 0/2] net: bring back dev_addr_sem
Kohei reports an issue with dev_addr_sem conversion to netdev instance
lock in [0]. Based on the discussion, switching to netdev instance
lock to protect the address might not work for the devices that
are not using netdev ops lock.
Bring dev_addr_sem instance lock back but fix the ordering.
0: https://lore.kernel.org/netdev/20250308203835.60633-2-enjuk@amazon.com
Stanislav Fomichev (2):
Revert "net: replace dev_addr_sem with netdev instance lock"
net: reorder dev_addr_sem lock
drivers/net/tap.c | 2 +-
drivers/net/tun.c | 2 +-
include/linux/netdevice.h | 4 +++-
net/core/dev.c | 41 +++++++++++++--------------------------
net/core/dev.h | 3 ++-
net/core/dev_api.c | 19 ++++++++++++++++--
net/core/dev_ioctl.c | 2 +-
net/core/net-sysfs.c | 7 +++++--
net/core/rtnetlink.c | 17 +++++++++++-----
9 files changed, 56 insertions(+), 41 deletions(-)
--
2.48.1
Powered by blists - more mailing lists