From: "David S. Miller" <davem@redhat.com>
To: "Simon Barber" <simon@instant802.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, bdschuym@pandora.be
Subject: Re: [PATCH 2.4.26-pre1] Allow ebtables module to change protocol in netif_receive_skb
Date: Thu, 26 Feb 2004 11:57:09 -0800 [thread overview]
Message-ID: <20040226115709.4ed1594d.davem@redhat.com> (raw)
In-Reply-To: <AC8C1F46CD753F4AAC8F890E35A9EB461C670B@webmail.instant802.com>
On Wed, 25 Feb 2004 14:47:41 -0800
"Simon Barber" <simon@instant802.com> wrote:
> Currently skb->protocol is read before the bridge is called, even though
> it's not used until after. Hence if an ebtables module changes the
> protocol of a frame the wrong protocol is interpreted.
Applied, even though ebtables is not in 2.4.x yet the change is valid.
I've applied your 2.6.x variant too of course.
Thanks Simon.
prev parent reply other threads:[~2004-02-26 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 22:47 [PATCH 2.4.26-pre1] Allow ebtables module to change protocol in netif_receive_skb Simon Barber
2004-02-26 19:57 ` David S. Miller [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=20040226115709.4ed1594d.davem@redhat.com \
--to=davem@redhat.com \
--cc=bdschuym@pandora.be \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=simon@instant802.com \
/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;
as well as URLs for NNTP newsgroup(s).