[PATCH net 0/6] rxrpc: Miscellaneous fixes
STALE3708d
From: David Howells <dhowells@redhat.com>
Date: 2016-08-09 16:33:17
Also in:
lkml
Revision v1 of 29 in this series.
Revisions (29)
- v1 current
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v3 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v2 [diff vs current]
- v1 [diff vs current]
- v2 [diff vs current]
- v1 [diff vs current]
- v2 [diff vs current]
- v3 [diff vs current]
- v4 [diff vs current]
- v5 [diff vs current]
- v1 [diff vs current]
- v2 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v1 [diff vs current]
- v2 [diff vs current]
- v3 [diff vs current]
- v9 [diff vs current]
- v10 [diff vs current]
- v11 [diff vs current]
Hi Dave,
Here are a bunch of miscellaneous fixes to AF_RXRPC:
(*) Fix an uninitialised pointer.
(*) Fix error handling when we fail to connect a call.
(*) Fix a NULL pointer dereference.
(*) Fix two occasions where a packet is accessed again after being queued
for someone else to deal with.
(*) Fix a missing skb free.
---
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-fixes
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-fixes-20160809
David
---
Arnd Bergmann (1):
rxrpc: fix uninitialized pointer dereference in debug code
David Howells (5):
rxrpc: Need to flag call as being released on connect failure
rxrpc: Don't access connection from call if pointer is NULL
rxrpc: Once packet posted in data_ready, don't retry posting
rxrpc: Fix a use-after-push in data_ready handler
rxrpc: Free packets discarded in data_ready
net/rxrpc/call_event.c | 4 ++++
net/rxrpc/call_object.c | 3 +++
net/rxrpc/input.c | 27 ++++++++++++++++-----------
3 files changed, 23 insertions(+), 11 deletions(-)