diff options
author | Vladimir Oltean <olteanv@gmail.com> | 2019-05-11 23:14:46 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-05-12 13:19:46 -0700 |
commit | 506f0e09ce36477ac610b6e9b52cbd4d5ead0c01 (patch) | |
tree | 26c66683788758d1f30cfbf619611c2cf6483049 /include/net/compat.h | |
parent | 87671375108625bb7f8a09f0809a369d460ebe43 (diff) | |
download | linux-stable-506f0e09ce36477ac610b6e9b52cbd4d5ead0c01.tar.gz linux-stable-506f0e09ce36477ac610b6e9b52cbd4d5ead0c01.tar.bz2 linux-stable-506f0e09ce36477ac610b6e9b52cbd4d5ead0c01.zip |
net: dsa: Remove dangerous DSA_SKB_CLONE() macro
This does not cause any bug now because it has no users, but its body
contains two pointer definitions within a code block:
struct sk_buff *clone = _clone; \
struct sk_buff *skb = _skb; \
When calling the macro as DSA_SKB_CLONE(clone, skb), these variables
would obscure the arguments that the macro was called with, and the
initializers would be a no-op instead of doing their job (undefined
behavior, by the way, but GCC nicely puts NULL pointers instead).
So simply remove this broken macro and leave users to simply call
"DSA_SKB_CB(skb)->clone = clone" by hand when needed.
There is one functional difference when doing what I just suggested
above: the control block won't be transferred from the original skb into
the clone. Since there's no foreseen need for the control block in the
clone ATM, this is ok.
Fixes: b68b0dd0fb2d ("net: dsa: Keep private info in the skb->cb")
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/net/compat.h')
0 files changed, 0 insertions, 0 deletions