diff options
| author | Julian Wiedmann <jwi@linux.ibm.com> | 2018-09-05 16:55:11 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-09-05 22:32:22 -0700 |
| commit | b2f543949acd1ba64313fdad9e672ef47550d773 (patch) | |
| tree | d74f5146a3c826668397c59eca92b492a34e13c9 /net/iucv/iucv.c | |
| parent | 222440996d6daf635bed6cb35041be22ede3e8a0 (diff) | |
| download | linux-b2f543949acd1ba64313fdad9e672ef47550d773.tar.bz2 | |
net/af_iucv: fix skb handling on HiperTransport xmit error
When sending an skb, afiucv_hs_send() bails out on various error
conditions. But currently the caller has no way of telling whether the
skb was freed or not - resulting in potentially either
a) leaked skbs from iucv_send_ctrl(), or
b) double-free's from iucv_sock_sendmsg().
As dev_queue_xmit() will always consume the skb (even on error), be
consistent and also free the skb from all other error paths. This way
callers no longer need to care about managing the skb.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Reviewed-by: Ursula Braun <ubraun@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/iucv/iucv.c')
0 files changed, 0 insertions, 0 deletions