summaryrefslogtreecommitdiff
path: root/drivers/pcmcia/pcmcia_resource.c
diff options
context:
space:
mode:
authorNeil Horman <nhorman@tuxdriver.com>2013-03-01 07:44:08 (GMT)
committerDavid S. Miller <davem@davemloft.net>2013-03-01 20:56:29 (GMT)
commitd8c6f4b9b7848bca8babfc0ae43a50c8ab22fbb9 (patch)
treec354b5edc7c4c335bea3d9dcf4e977646ed012a0 /drivers/pcmcia/pcmcia_resource.c
parent9e0aab86496295efdf6c2f57eaac3497e1c721a2 (diff)
downloadlinux-fsl-qoriq-d8c6f4b9b7848bca8babfc0ae43a50c8ab22fbb9.tar.xz
ipv[4|6]: correct dropwatch false positive in local_deliver_finish
I had a report recently of a user trying to use dropwatch to localise some frame loss, and they were getting false positives. Turned out they were using a user space SCTP stack that used raw sockets to grab frames. When we don't have a registered protocol for a given packet, we record it as a drop, even if a raw socket receieves the frame. We should only record the drop in the event a raw socket doesnt exist to receive the frames Tested by the reported successfully Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Reported-by: William Reich <reich@ulticom.com> Tested-by: William Reich <reich@ulticom.com> CC: "David S. Miller" <davem@davemloft.net> CC: William Reich <reich@ulticom.com> CC: eric.dumazet@gmail.com Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/pcmcia/pcmcia_resource.c')
0 files changed, 0 insertions, 0 deletions