summaryrefslogtreecommitdiff
path: root/bpf_jit_disasm.c
AgeCommit message (Expand)AuthorFilesLines
2013-05-27bpf: add minimal BPF JIT emitted image disassemblerDaniel Borkmann1-0/+207
tr>
authorSabrina Dubroca <sd@queasysnail.net>2016-08-12 16:10:33 +0200
committerDavid S. Miller <davem@davemloft.net>2016-08-13 15:15:54 -0700
commit952fcfd08c8109951622579d0ae7b9cd6cafd688 (patch)
tree16e787138d3da28899e3a0028962928c79a4af07
parente20038724552cd05e351cd7d7526d646953d26b7 (diff)
net: remove type_check from dev_get_nest_level()
The idea for type_check in dev_get_nest_level() was to count the number of nested devices of the same type (currently, only macvlan or vlan devices). This prevented the false positive lockdep warning on configurations such as: eth0 <--- macvlan0 <--- vlan0 <--- macvlan1 However, this doesn't prevent a warning on a configuration such as: eth0 <--- macvlan0 <--- vlan0 eth1 <--- vlan1 <--- macvlan1 In this case, all the locks end up with a nesting subclass of 1, so lockdep thinks that there is still a deadlock: - in the first case we have (macvlan_netdev_addr_lock_key, 1) and then take (vlan_netdev_xmit_lock_key, 1) - in the second case, we have (vlan_netdev_xmit_lock_key, 1) and then take (macvlan_netdev_addr_lock_key, 1) By removing the linktype check in dev_get_nest_level() and always incrementing the nesting depth, lockdep considers this configuration valid. Signed-off-by: Sabrina Dubroca <sd@queasysnail.net> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat