From: "David S. Miller" <davem@redhat.com>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: ebtables-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [PATCH] 2.6.3 fix vlan-encapsulated fragmented IP traffic
Date: Sun, 29 Feb 2004 21:54:21 -0800 [thread overview]
Message-ID: <20040229215421.0ca987e8.davem@redhat.com> (raw)
In-Reply-To: <200402291914.53578.bdschuym@pandora.be>
On Sun, 29 Feb 2004 19:14:53 +0100
Bart De Schuymer <bdschuym@pandora.be> wrote:
> When vlan-tagged fragmented IP traffic passes the bridging firewall and
> ip_conntrack is loaded and iptables sees this IP traffic, an oops can
> occur when trying to fragment the defragmented packets. This only
> happens in the slow_path of ip_fragment().
...
> The patch below fixes it. I saw no other way than to add some code to
> ip_fragment(), but this extra code is located in the slow_path so it's
> hardly ever executed.
Can you explain the 'mtu' fiddling a little bit? I think it's correct...
but you know :)
The one case I'm concerned about is when the device does hw acceleration
of vlan tagging (ie. therefore things are transparent supposedly), is
the 'mtu' adjustment thing correct in that case?
I'm applying this for now, as I can't come up with a better fix either.
If we find a problem with this change, we'll fix that up.
I'm really concerned, btw, that this is going to propagate to other places
as well, what if something that gets handled this way gets sent over an
IPIP tunnel via some route, and then IPIP has to make all of these crazy
adjustments too? That's going too far and we'll have to find a better
way if that is the case.
next prev parent reply other threads:[~2004-03-01 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 18:14 [PATCH] 2.6.3 fix vlan-encapsulated fragmented IP traffic Bart De Schuymer
2004-03-01 5:54 ` David S. Miller [this message]
[not found] ` <20040229215421.0ca987e8.davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2004-03-01 7:06 ` Bart De Schuymer
2004-03-01 8:35 ` David S. Miller
[not found] ` <20040301003525.522d6db2.davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2004-03-01 18:47 ` Bart De Schuymer
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=20040229215421.0ca987e8.davem@redhat.com \
--to=davem@redhat.com \
--cc=bdschuym@pandora.be \
--cc=ebtables-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.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).