summaryrefslogtreecommitdiffstats
path: root/tools/power
diff options
context:
space:
mode:
authorEyal Birger <eyal.birger@gmail.com>2015-03-01 14:58:27 +0200
committerDavid S. Miller <davem@davemloft.net>2015-03-02 00:19:29 -0500
commit2cfdf9fcb85bf6c0bb4556384ba800b9f443f601 (patch)
tree7a465e8f0cfb8cf26b4601348038e0a24bece904 /tools/power
parent6368c235777456ddaeaa61360186d8d03a61cb18 (diff)
downloadop-kernel-dev-2cfdf9fcb85bf6c0bb4556384ba800b9f443f601.zip
op-kernel-dev-2cfdf9fcb85bf6c0bb4556384ba800b9f443f601.tar.gz
net: rxrpc: change call to sock_recv_ts_and_drops() on rxrpc recvmsg to sock_recv_timestamp()
Commit 3b885787ea4112 ("net: Generalize socket rx gap / receive queue overflow cmsg") allowed receiving packet dropcount information as a socket level option. RXRPC sockets recvmsg function was changed to support this by calling sock_recv_ts_and_drops() instead of sock_recv_timestamp(). However, protocol families wishing to receive dropcount should call sock_queue_rcv_skb() or set the dropcount specifically (as done in packet_rcv()). This was not done for rxrpc and thus this feature never worked on these sockets. Formalizing this by not calling sock_recv_ts_and_drops() in rxrpc as part of an effort to move skb->dropcount into skb->cb[] Signed-off-by: Eyal Birger <eyal.birger@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/power')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud