From: "L. A. Walsh" <lkml@tlinx•org>
To: Linux Kernel Network Developers <netdev@vger•kernel.org>
Subject: WARNING: iputils is not very fresh, upgrade is recommended; bug in iputils or kernel?
Date: Wed, 30 Sep 2015 17:46:26 -0700 [thread overview]
Message-ID: <560C8262.6030405@tlinx.org> (raw)
According to the comment in the code:
---
/* Sigh, IP_RECVERR for raw socket
* was broken until 2.4.9. So, we ignore
* the first error and warn on the second.
*/
if (once++ == 1)
fprintf(stderr, "\rWARNING: kernel is not very fresh,
upgrade is recommended.\n");
----
When I first saw the error I wondered how fresh my kernel had
to be to pass iputils' tests, since I'm running on:
Ishtar:packages/build/iputils-s20121221> uname -a
Linux Ishtar 4.1.0-Isht-Van #2 SMP PREEMPT Tue Jun 23 07:52:09 PDT 2015
x86_64 x86_64 x86_64 GNU/Linux
So I looked at code Um... why is iputils thinking
that 4.1.0 < 2.4.9 -- or that 4.1.0 is older than
2.4.9?
I humbly submit that 4.1.0, released in 2015 is
unquestionably 'fresher' than the date on iputils of 2012.
Does this mean the check in iputils is faulty w/r/t new
kernels, or do new kernels have a *SERIOUS* regression?
reply other threads:[~2015-10-01 1:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560C8262.6030405@tlinx.org \
--to=lkml@tlinx$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox