Descriptionsyscall: fix ParseRoutingSockaddr with unexpected submessages
No easy way to test (would have to actually trigger some routing
events from kernel) but the code is clearly wrong as written.
If the header says there is a submessage, we need to at least
skip over its bytes, not just continue to the next iteration.
Fixes issue 8203.
Patch Set 1 #Patch Set 2 : diff -r 0e9f68c2b11dba5fcbe067ffc8a674fbdd21ee84 https://code.google.com/p/go/ #Patch Set 3 : diff -r 0e9f68c2b11dba5fcbe067ffc8a674fbdd21ee84 https://code.google.com/p/go/ #Patch Set 4 : diff -r 0e9f68c2b11dba5fcbe067ffc8a674fbdd21ee84 https://code.google.com/p/go/ #MessagesTotal messages: 4
|