* [PATCH] Inconsistent behaviour at AF_PACKET
@ 2007-08-01 19:00 Unai Uribarri
0 siblings, 0 replies; only message in thread
From: Unai Uribarri @ 2007-08-01 19:00 UTC (permalink / raw)
To: netdev
Hello folks,
Timestamps should be usually requested explicitly by setting the
SOL_SOCKET/SO_TIMESTAMP option to 1. But if you setup a reception ring
with the SOL_PACKET/PACKET_RX_RING option, timestamps are automatically
enabled at the next packet recepcion.
I think that is a bug so I have written a patch that corrects it.
Thanks.
diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
index 1322d62..a4f2da3 100644
--- a/net/packet/af_packet.c
+++ b/net/packet/af_packet.c
@@ -640,10 +640,6 @@ static int tpacket_rcv(struct sk_buff *skb, struct
net_device *dev, struct packe
h->tp_snaplen = snaplen;
h->tp_mac = macoff;
h->tp_net = netoff;
- if (skb->tstamp.tv64 == 0) {
- __net_timestamp(skb);
- sock_enable_timestamp(sk);
- }
tv = ktime_to_timeval(skb->tstamp);
h->tp_sec = tv.tv_sec;
h->tp_usec = tv.tv_usec;
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2007-08-01 19:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-01 19:00 [PATCH] Inconsistent behaviour at AF_PACKET Unai Uribarri
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox