Thread (4 messages) flat view 4 messages, 2 authors, 2016-06-21

Re: [PATCH] rxrpc: fix uninitialized variable use

From: Arnd Bergmann <arnd@arndb.de>
Date: 2016-06-21 09:27:43
Also in: lkml

On Tuesday, June 21, 2016 9:48:52 AM CEST David Howells wrote:
Arnd Bergmann [off-list ref] wrote:
quoted
Hashing the peer key was introduced for AF_INET, but gcc
warns about the rxrpc_peer_hash_key function returning uninitialized
data for any other value of srx->transport.family:

net/rxrpc/peer_object.c: In function 'rxrpc_peer_hash_key':
net/rxrpc/peer_object.c:57:15: error: 'p' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Assuming that nothing else can be set here, this changes the
function to just return zero in case of an unknown address
family.
I'm actually more tempted to put a BUG() in there because if any new family
support (say AF_INET6) is added, I want to make sure I catch all the places.
Makes sense. Do you want to do the patch yourself, or should I send
a new one doing that?

Maybe WARN() would be better than BUG()? That would still get the attention
it needs but not kill the process.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help