Re: [PATCH] rxrpc: fix uninitialized variable use

2016-06-21 Thread David Howells
Arnd Bergmann wrote: > > 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? >

Re: [PATCH] rxrpc: fix uninitialized variable use

2016-06-21 Thread Arnd Bergmann
On Tuesday, June 21, 2016 9:48:52 AM CEST David Howells wrote: > Arnd Bergmann wrote: > > > 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: > >

Re: [PATCH] rxrpc: fix uninitialized variable use

2016-06-21 Thread David Howells
Arnd Bergmann wrote: > 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': >

[PATCH] rxrpc: fix uninitialized variable use

2016-06-17 Thread Arnd Bergmann
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