From: Stephen Hemminger <stephen@networkplumber.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
jiri@resnulli.us, sd@queasysnail.net, roopa@cumulusnetworks.com,
saeedm@mellanox.com, manishc@marvell.com, rahulv@marvell.com,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, sashal@kernel.org, hare@suse.de,
varun@chelsio.com, ubraun@linux.ibm.com, kgraul@linux.ibm.com
Subject: Re: [PATCH net 00/11] net: fix nested device bugs
Date: Wed, 4 Sep 2019 11:58:39 -0700 [thread overview]
Message-ID: <20190904115839.64c27609@hermes.lan> (raw)
In-Reply-To: <20190904183828.14260-1-ap420073@gmail.com>
On Thu, 5 Sep 2019 03:38:28 +0900
Taehee Yoo <ap420073@gmail.com> wrote:
> This patchset fixes several bugs that are related to nesting
> device infrastructure.
> Current nesting infrastructure code doesn't limit the depth level of
> devices. nested devices could be handled recursively. at that moment,
> it needs huge memory and stack overflow could occur.
> Below devices type have same bug.
> VLAN, BONDING, TEAM, MACSEC, MACVLAN and VXLAN.
>
> Test commands:
> ip link add dummy0 type dummy
> ip link add vlan1 link dummy0 type vlan id 1
>
> for i in {2..100}
> do
> let A=$i-1
> ip link add name vlan$i link vlan$A type vlan id $i
> done
> ip link del dummy0
>
> 1st patch actually fixes the root cause.
> It adds new common variables {upper/lower}_level that represent
> depth level. upper_level variable is depth of upper devices.
> lower_level variable is depth of lower devices.
>
> [U][L] [U][L]
> vlan1 1 5 vlan4 1 4
> vlan2 2 4 vlan5 2 3
> vlan3 3 3 |
> | |
> +------------+
> |
> vlan6 4 2
> dummy0 5 1
>
> After this patch, the nesting infrastructure code uses this variable to
> check the depth level.
>
> 2, 4, 5, 6, 7 patches fix lockdep related problem.
> Before this patch, devices use static lockdep map.
> So, if devices that are same type is nested, lockdep will warn about
> recursive situation.
> These patches make these devices use dynamic lockdep key instead of
> static lock or subclass.
>
> 3rd patch splits IFF_BONDING flag into IFF_BONDING and IFF_BONDING_SLAVE.
> Before this patch, there is only IFF_BONDING flags, which means
> a bonding master or a bonding slave device.
> But this single flag could be problem when bonding devices are set to
> nested.
>
> 8th patch fixes a refcnt leak in the macsec module.
>
> 9th patch adds ignore flag to an adjacent structure.
> In order to exchange an adjacent node safely, ignore flag is needed.
>
> 10th patch makes vxlan add an adjacent link to limit depth level.
>
> 11th patch removes unnecessary variables and callback.
>
> Taehee Yoo (11):
> net: core: limit nested device depth
> vlan: use dynamic lockdep key instead of subclass
> bonding: split IFF_BONDING into IFF_BONDING and IFF_BONDING_SLAVE
> bonding: use dynamic lockdep key instead of subclass
> team: use dynamic lockdep key instead of static key
> macsec: use dynamic lockdep key instead of subclass
> macvlan: use dynamic lockdep key instead of subclass
> macsec: fix refcnt leak in module exit routine
> net: core: add ignore flag to netdev_adjacent structure
> vxlan: add adjacent link to limit depth level
> net: remove unnecessary variables and callback
>
> drivers/net/bonding/bond_alb.c | 2 +-
> drivers/net/bonding/bond_main.c | 87 ++++--
> .../net/ethernet/mellanox/mlx5/core/en_tc.c | 2 +-
> .../ethernet/qlogic/netxen/netxen_nic_main.c | 2 +-
> drivers/net/hyperv/netvsc_drv.c | 3 +-
> drivers/net/macsec.c | 50 ++--
> drivers/net/macvlan.c | 36 ++-
> drivers/net/team/team.c | 61 ++++-
> drivers/net/vxlan.c | 71 ++++-
> drivers/scsi/fcoe/fcoe.c | 2 +-
> drivers/target/iscsi/cxgbit/cxgbit_cm.c | 2 +-
> include/linux/if_macvlan.h | 3 +-
> include/linux/if_team.h | 5 +
> include/linux/if_vlan.h | 13 +-
> include/linux/netdevice.h | 29 +-
> include/net/bonding.h | 4 +-
> include/net/vxlan.h | 1 +
> net/8021q/vlan.c | 1 -
> net/8021q/vlan_dev.c | 32 +--
> net/core/dev.c | 252 ++++++++++++++++--
> net/core/dev_addr_lists.c | 12 +-
> net/smc/smc_core.c | 2 +-
> net/smc/smc_pnet.c | 2 +-
> 23 files changed, 519 insertions(+), 155 deletions(-)
>
The network receive path already avoids excessive stack
depth. Maybe the real problem is in the lockdep code.
next prev parent reply other threads:[~2019-09-04 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 18:38 [PATCH net 00/11] net: fix nested device bugs Taehee Yoo
2019-09-04 18:58 ` Stephen Hemminger [this message]
2019-09-05 9:15 ` Taehee Yoo
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=20190904115839.64c27609@hermes.lan \
--to=stephen@networkplumber.org \
--cc=andy@greyhouse.net \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=hare@suse.de \
--cc=j.vosburgh@gmail.com \
--cc=jiri@resnulli.us \
--cc=kgraul@linux.ibm.com \
--cc=kys@microsoft.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rahulv@marvell.com \
--cc=roopa@cumulusnetworks.com \
--cc=saeedm@mellanox.com \
--cc=sashal@kernel.org \
--cc=sd@queasysnail.net \
--cc=sthemmin@microsoft.com \
--cc=ubraun@linux.ibm.com \
--cc=varun@chelsio.com \
--cc=vfalico@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).