From: Alan Cox <alan@redhat.com>
To: ashishk@caldera.com (Ashish Kalra)
Cc: davem@redhat.com, ak@muc.de, linux-kernel@vger.kernel.org,
alan@redhat.com, akpm@zip.com.au, jgarzik@mandrakesoft.com,
linux-net@vger.kernel.org, ashishk@sco.com
Subject: Re: EtherLeak generic fix - for feedback & testing.
Date: Thu, 13 Feb 2003 13:37:18 -0500 (EST) [thread overview]
Message-ID: <200302131837.h1DIbIh14604@devserv.devel.redhat.com> (raw)
In-Reply-To: <3.0.32.20030213175200.006cf7cc@indus.asia.caldera.com> from "Ashish Kalra" at Feb 13, 2003 05:52:06 PM
> This is a kernel-2.4.13 patch for a "generic" fix for the Etherleak security
> issue and it works without making modifications to network device drivers.
The right approach is to fix all the drivers so thats what we did. I can
see why a distro fix for an ancient kernel would be done the way you did
though.
prev parent reply other threads:[~2003-02-13 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 12:52 EtherLeak generic fix - for feedback & testing Ashish Kalra
2003-02-13 12:09 ` David S. Miller
2003-02-14 9:03 ` Roger Luethi
2003-02-13 18:37 ` Alan Cox [this message]
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=200302131837.h1DIbIh14604@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=ak@muc.de \
--cc=akpm@zip.com.au \
--cc=ashishk@caldera.com \
--cc=ashishk@sco.com \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.