diff options
author | Richard Cochran <richardcochran@gmail.com> | 2011-10-21 00:49:15 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-10-24 02:54:50 -0400 |
commit | da92b194cc36b5dc1fbd85206aeeffd80bee0c39 (patch) | |
tree | 375ead604156d8a8afc5ecef8d76415e999ce903 /net/ipv4 | |
parent | f7ff19871bb4a3451e1ca2cf660bf633018cfbec (diff) | |
download | op-kernel-dev-da92b194cc36b5dc1fbd85206aeeffd80bee0c39.zip op-kernel-dev-da92b194cc36b5dc1fbd85206aeeffd80bee0c39.tar.gz |
net: hold sock reference while processing tx timestamps
The pair of functions,
* skb_clone_tx_timestamp()
* skb_complete_tx_timestamp()
were designed to allow timestamping in PHY devices. The first
function, called during the MAC driver's hard_xmit method, identifies
PTP protocol packets, clones them, and gives them to the PHY device
driver. The PHY driver may hold onto the packet and deliver it at a
later time using the second function, which adds the packet to the
socket's error queue.
As pointed out by Johannes, nothing prevents the socket from
disappearing while the cloned packet is sitting in the PHY driver
awaiting a timestamp. This patch fixes the issue by taking a reference
on the socket for each such packet. In addition, the comments
regarding the usage of these function are expanded to highlight the
rule that PHY drivers must use skb_complete_tx_timestamp() to release
the packet, in order to release the socket reference, too.
These functions first appeared in v2.6.36.
Reported-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Richard Cochran <richard.cochran@omicron.at>
Cc: <stable@vger.kernel.org>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions