From: "David S. Miller" <davem@redhat.com>
To: marcelo@conectiva.com.br
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18-pre6
Date: Tue, 22 Jan 2002 22:17:51 -0800 (PST) [thread overview]
Message-ID: <20020122.221751.45130206.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0201221902250.2262-100000@freak.distro.conectiva>
In-Reply-To: <20020122220046.C21383@flint.arm.linux.org.uk> <Pine.LNX.4.21.0201221902250.2262-100000@freak.distro.conectiva>
From: Marcelo Tosatti <marcelo@conectiva.com.br>
Date: Tue, 22 Jan 2002 19:03:04 -0200 (BRST)
On Tue, 22 Jan 2002, Russell King wrote:
> Can you enlighten us as to why it is "not needed" ? I haven't seen any
> followups from Andi nor Davem to saying that.
David told me the patch is not needed and only 2.2.x and 2.4.0-pre are
affected.
David?
Correct. The 2.3.x/2.4.x branch of the code had the fix made in
revision 1.71 of net/ipv4/icmp.c which equates to August 8th, 2000
which equates to 2.4.0-test6-pre2 or -pre3. :-)
On the 2.2.x side, 2.2.18 has the fix. There is one, and only one
change, in that patch, to the file net/ipv4/icmp.c and it is the
fix in question.
It is really unfortunate that the bugtraq reporter failed to even
bother to mention what kernel he was using. It could have avoided a
lot of the confusion surrounding this (already fixed) bug.
next prev parent reply other threads:[~2002-01-23 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 18:06 Linux 2.4.18-pre6 Marcelo Tosatti
2002-01-22 22:00 ` Russell King
2002-01-22 21:03 ` Marcelo Tosatti
2002-01-23 6:17 ` David S. Miller [this message]
2002-01-22 22:32 ` Erik Andersen
2002-01-22 23:07 ` Linux 2.4.18-pre6 - unresolved symbols Eyal Lebedinsky
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=20020122.221751.45130206.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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