| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1400261568.7973.225.camel@edumazet-glaptop2.roam.corp.google.com> Date: Fri, 16 May 2014 10:32:48 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Vlad Yasevich <vyasevic@...hat.com> Cc: netdev@...r.kernel.org, dingtianhong@...wei.com, kaber@...sh.net, vfalico@...il.com, jiri@...nulli.us Subject: Re: [PATCH v2 1/4] net: Find the nesting level of a given device by type. On Fri, 2014-05-16 at 13:18 -0400, Vlad Yasevich wrote: > Multiple devices in the kernel can be stacked/nested and they > need to know their nesting level for the purposes of lockdep. > This patch provides a generic function that determines a nesting > level of a particular device by its type (ex: vlan, macvlan, etc). > We only care about nesting of the same type of devices. > > For example: > eth0 <- vlan0.10 <- macvlan0 <- vlan1.20 > > The nesting level of vlan1.20 would be 1, since there is another vlan > in the stack under it. > > Signed-off-by: Vlad Yasevich <vyasevic@...hat.com> > --- > include/linux/netdevice.h | 10 ++++++++++ > net/core/dev.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 58 insertions(+) Nice, but if LOCKDEP is not used, do we really want to have dev_get_nest_level() being something else than a constant ? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists