diff options
author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2019-02-04 13:20:29 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-02-04 19:54:52 +0300 |
commit | 53bc8d2af08654659abfadfd3e98eb9922ff787c (patch) | |
tree | 206e73d60d0522d51feb3abea5a5b429d0ea65ea /net/smc | |
parent | 546f28974d771b124fb0bf7b551b343888cf0419 (diff) | |
download | linux-53bc8d2af08654659abfadfd3e98eb9922ff787c.tar.xz |
net: dp83640: expire old TX-skb
During sendmsg() a cloned skb is saved via dp83640_txtstamp() in
->tx_queue. After the NIC sends this packet, the PHY will reply with a
timestamp for that TX packet. If the cable is pulled at the right time I
don't see that packet. It might gets flushed as part of queue shutdown
on NIC's side.
Once the link is up again then after the next sendmsg() we enqueue
another skb in dp83640_txtstamp() and have two on the list. Then the PHY
will send a reply and decode_txts() attaches it to the first skb on the
list.
No crash occurs since refcounting works but we are one packet behind.
linuxptp/ptp4l usually closes the socket and opens a new one (in such a
timeout case) so those "stale" replies never get there. However it does
not resume normal operation anymore.
Purge old skbs in decode_txts().
Fixes: cb646e2b02b2 ("ptp: Added a clock driver for the National Semiconductor PHYTER.")
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de>
Acked-by: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/smc')
0 files changed, 0 insertions, 0 deletions