Arnd Bergmann wrote:
> I'll follow up with the fixes, both of which are rather
> straightforward.
Are they both in?
[PATCH 2/2] rxrpc: fix undefined behavior in rxrpc_mark_call_released
David
On Sunday, August 28, 2016 9:42:17 AM CEST David Howells wrote:
> This is fixed by:
>
> commit 2266ffdef5737fdfa96005204fc5606dbd559956
> subject: rxrpc: Fix conn-based retransmit
>
> which is in net-next.
I've merged net-next into the last linux-next release now for
testing (no
This is fixed by:
commit 2266ffdef5737fdfa96005204fc5606dbd559956
subject: rxrpc: Fix conn-based retransmit
which is in net-next.
David
Arnd Bergmann wrote:
> A change to the retransmission handling in rxrpc caused a use-before-init
> bug in rxrpc_data_ready(), as indicated by "gcc -Wmaybe-uninitialized":
>
> net/rxrpc/input.c: In function 'rxrpc_data_ready':
> net/rxrpc/input.c:735:34: error: 'call' may be used uninitialized in
A change to the retransmission handling in rxrpc caused a use-before-init
bug in rxrpc_data_ready(), as indicated by "gcc -Wmaybe-uninitialized":
net/rxrpc/input.c: In function 'rxrpc_data_ready':
net/rxrpc/input.c:735:34: error: 'call' may be used uninitialized in this
function [-Werror=maybe-un
