confusing kdump output

[Michiel Boland]

Hi. If a program does something like

setsockopt(sock, IPPROTO_TCP, TCP_NOPUSH, &onoff, sizeof onoff)

this is reported by kdump as

setsockopt(0x2a,0x6,SO_REUSEADDR,0x7fffffffe32c,0x4)

Note that it reports SO_REUSEADDR rather than TCP_NOPUSH. This is 
confusing.

It's probably a bit useless to compile all possible printable socket 
options into kdump, but at least it could be made to not print a symbolic 
name if the level is, say, not SOL_SOCKET.

Cheers
Michiel