* Bug in IPv4 version of ping...
@ 2014-02-03 10:31 Vic
0 siblings, 0 replies; only message in thread
From: Vic @ 2014-02-03 10:31 UTC (permalink / raw)
To: netdev
Hi All.
I hope this is the right place to post this - this list is mentioned as
the mailing list for iputils.
I believe I've found a bug in ping.c - there is an ancient work-around for
an IP_RECVERR bug in raw sockets. The problem is as follows :-
ping_common.c defines a variable working_recverr
ping.c uses this variable to work out what it should do under certain
failure circumstances.
As far as I can see, working_recverr is undefined when first used; the
initial response to it could be either way. This leads to an erroneous
report that the kernel is "not very fresh", and needs to be upgraded.
I have seen this in the current builds for RHEL5 and 6 (s20071127) and in
the current release (s20121221).
I suspect this variable should be set somewhere after option parsing...
HTH
Vic.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-02-03 11:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-03 10:31 Bug in IPv4 version of ping Vic
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).