From: Patrick McHardy <kaber@trash.net>
To: Wei Yongjun <weiyj@soft.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]ip_options_fragment() has no effect on fragmentation
Date: Thu, 26 Jan 2006 09:46:07 +0100 [thread overview]
Message-ID: <43D88C4F.7080302@trash.net> (raw)
In-Reply-To: <0a3101c6229a$3cc7c1b0$cfa0220a@WeiYJ>
Wei Yongjun wrote:
> [1]Summary of the problem:
> ip_options_fragment() has no effect on fragmentation
>
> [2]Full description of the problem:
> When I send IPv4 packet(contain Record Route Option) which need to be
> fragmented to the router, the router can not fragment it correctly.
> After fragmented by router, the second fragmentation still contain
> Record Route Option. Refer to RFC791, Record Route Option must Not be
> copied on fragmentation, goes in first fragment only.
> ip_options_fragment() is the implemental function, but there are some
> BUGs in it:
>
> ip_option.c: line 207:
> void ip_options_fragment(struct sk_buff * skb)
> {
> unsigned char * optptr = skb->nh.raw;
> struct ip_options * opt = &(IPCB(skb)->opt);
> ...
>
> optptr get a error pointer to the ipv4 options, correct is as following:
>
> unsigned char * optptr = skb->nh.raw + sizeof(struct iphdr);
>
> By the way, ip_options_fragment() just fill options not allowed in
> fragments with NOOPs, does not delete the space of the options,
> following patch has corrected the problem.
Please split the optptr fix and your enhancements in two patches and
send them to netdev@vger.kernel.org.
BTW, your mailer corrupts whitespace.
next prev parent reply other threads:[~2006-01-26 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:02 [PATCH]ip_options_fragment() has no effect on fragmentation Wei Yongjun
2006-01-26 5:59 ` Eric Dumazet
2006-01-26 8:46 ` Patrick McHardy [this message]
[not found] <001701c6277a$eaa93950$cfa0220a@WeiYJ>
[not found] ` <1138821701.3852.8.camel@L-tech1>
[not found] ` <20060202.170840.114568749.davem@davemloft.net>
2006-05-05 17:50 ` weiyj
2006-05-08 5:39 ` David S. Miller
2006-05-08 5:41 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-05-06 0:36 Wei Yongjun
2006-05-09 22:20 ` David S. Miller
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=43D88C4F.7080302@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=weiyj@soft.fujitsu.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 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.