From: David Miller <davem@davemloft.net>
To: ap420073@gmail.com
Cc: 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,
jay.vosburgh@canonical.com
Subject: Re: [PATCH net v2 01/11] net: core: limit nested device depth
Date: Thu, 12 Sep 2019 11:38:07 +0200 (CEST) [thread overview]
Message-ID: <20190912.113807.52193745382103083.davem@davemloft.net> (raw)
In-Reply-To: <CAMArcTV-Qvfd7xA0huCh_dbtr7P4LA+cQ7CpnaBBhdq-tq5fZQ@mail.gmail.com>
From: Taehee Yoo <ap420073@gmail.com>
Date: Thu, 12 Sep 2019 12:56:19 +0900
> I tested with this reproducer commands without lockdep.
>
> ip link add dummy0 type dummy
> ip link add link dummy0 name vlan1 type vlan id 1
> ip link set vlan1 up
>
> for i in {2..200}
> do
> let A=$i-1
>
> ip link add name vlan$i link vlan$A type vlan id $i
> done
> ip link del vlan1 <-- this command is added.
Is there any other device type which allows arbitrary nesting depth
in this manner other than VLAN? Perhaps it is the VLAN nesting
depth that we should limit instead of all of this extra code.
next prev parent reply other threads:[~2019-09-12 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 13:45 [PATCH net v2 01/11] net: core: limit nested device depth Taehee Yoo
2019-09-11 22:32 ` David Miller
2019-09-12 3:56 ` Taehee Yoo
2019-09-12 9:38 ` David Miller [this message]
2019-09-12 10:14 ` Taehee Yoo
2019-09-12 11:37 ` David Miller
2019-09-12 11:54 ` Taehee Yoo
2019-09-12 12:49 ` 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=20190912.113807.52193745382103083.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=ap420073@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=hare@suse.de \
--cc=j.vosburgh@gmail.com \
--cc=jay.vosburgh@canonical.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).