rxrpc: fix undefined behavior in rxrpc_mark_call_released
authorArnd Bergmann <arnd@arndb.de>
Fri, 2 Sep 2016 21:39:44 +0000 (22:39 +0100)
committerDavid Howells <dhowells@redhat.com>
Fri, 2 Sep 2016 21:39:44 +0000 (22:39 +0100)
commit30787a417086df301c7eb2f4ae14f2acab70e4b2
tree93ca81216d8294193bbd411dd620bb24756b2c00
parentdd19bde36739702bbd9a832b5d4995bc0fa8d6d7
rxrpc: fix undefined behavior in rxrpc_mark_call_released

gcc -Wmaybe-initialized correctly points out a newly introduced bug
through which we can end up calling rxrpc_queue_call() for a dead
connection:

net/rxrpc/call_object.c: In function 'rxrpc_mark_call_released':
net/rxrpc/call_object.c:600:5: error: 'sched' may be used uninitialized in this function [-Werror=maybe-uninitialized]

This sets the 'sched' variable to zero to restore the previous
behavior.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: f5c17aaeb2ae ("rxrpc: Calls should only have one terminal state")
Signed-off-by: David Howells <dhowells@redhat.com>
net/rxrpc/call_object.c
This page took 0.031651 seconds and 5 git commands to generate.