diff options
| author | David Howells <dhowells@redhat.com> | 2017-04-06 10:12:00 +0100 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2017-04-06 11:09:39 +0100 |
| commit | fb46f6ee10e78799ea38cf97e4bf52cb70f1228a (patch) | |
| tree | 070c369bd2417cc34c6e61b93e8567450406a55c /net/rxrpc/recvmsg.c | |
| parent | ef68622da9cc0c4e5202f90093a3a5314e41e9e9 (diff) | |
| download | linux-fb46f6ee10e78799ea38cf97e4bf52cb70f1228a.tar.gz linux-fb46f6ee10e78799ea38cf97e4bf52cb70f1228a.tar.bz2 linux-fb46f6ee10e78799ea38cf97e4bf52cb70f1228a.zip | |
rxrpc: Trace protocol errors in received packets
Add a tracepoint (rxrpc_rx_proto) to record protocol errors in received
packets. The following changes are made:
(1) Add a function, __rxrpc_abort_eproto(), to note a protocol error on a
call and mark the call aborted. This is wrapped by
rxrpc_abort_eproto() that makes the why string usable in trace.
(2) Add trace_rxrpc_rx_proto() or rxrpc_abort_eproto() to protocol error
generation points, replacing rxrpc_abort_call() with the latter.
(3) Only send an abort packet in rxkad_verify_packet*() if we actually
managed to abort the call.
Note that a trace event is also emitted if a kernel user (e.g. afs) tries
to send data through a call when it's not in the transmission phase, though
it's not technically a receive event.
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'net/rxrpc/recvmsg.c')
| -rw-r--r-- | net/rxrpc/recvmsg.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/net/rxrpc/recvmsg.c b/net/rxrpc/recvmsg.c index ad1a815b9706..f9caf3b77509 100644 --- a/net/rxrpc/recvmsg.c +++ b/net/rxrpc/recvmsg.c @@ -682,9 +682,11 @@ out: return ret; short_data: + trace_rxrpc_rx_eproto(call, 0, tracepoint_string("short_data")); ret = -EBADMSG; goto out; excess_data: + trace_rxrpc_rx_eproto(call, 0, tracepoint_string("excess_data")); ret = -EMSGSIZE; goto out; call_complete: |