diff options
| author | Eric Dumazet <[email protected]> | 2018-11-25 16:26:23 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2018-11-25 18:36:19 +0000 |
| commit | 4bffc669d6248d655aeb985a0e51bfaaf21c8b40 (patch) | |
| tree | 4e60ee772adb097ec25619769dcf4e02d8829fcb /tools/bpf/bpftool/prog.c | |
| parent | net: bridge: remove redundant checks for null p->dev and p->br (diff) | |
| download | kernel-4bffc669d6248d655aeb985a0e51bfaaf21c8b40.tar.gz kernel-4bffc669d6248d655aeb985a0e51bfaaf21c8b40.zip | |
net: remove unsafe skb_insert()
I do not see how one can effectively use skb_insert() without holding
some kind of lock. Otherwise other cpus could have changed the list
right before we have a chance of acquiring list->lock.
Only existing user is in drivers/infiniband/hw/nes/nes_mgt.c and this
one probably meant to use __skb_insert() since it appears nesqp->pau_list
is protected by nesqp->pau_lock. This looks like nesqp->pau_lock
could be removed, since nesqp->pau_list.lock could be used instead.
Signed-off-by: Eric Dumazet <[email protected]>
Cc: Faisal Latif <[email protected]>
Cc: Doug Ledford <[email protected]>
Cc: Jason Gunthorpe <[email protected]>
Cc: linux-rdma <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/bpf/bpftool/prog.c')
0 files changed, 0 insertions, 0 deletions