From: weiyj@soft.fujitsu.com
To: "David S. Miller" <davem@davemloft.net>
Cc: weiyj@soft.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [PATCH]ip_options_fragment() has no effect on fragmentation
Date: Fri, 5 May 2006 13:50:02 -0400 [thread overview]
Message-ID: <200605051350.03300.weiyj@soft.fujitsu.com> (raw)
In-Reply-To: <20060202.170840.114568749.davem@davemloft.net>
Hello Mr. David:
Does this patch will be used?
This patch resolved the following 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.
On Thursday 02 February 2006 20:08, David S. Miller wrote:
> From: Wei Yongjun <weiyj@soft.fujitsu.com>
> Date: Wed, 01 Feb 2006 14:21:41 -0500
>
> Your patch is still corrupt, new lines were added by your email client
> which splits up the patch headers.
>
> I applied the patch by hand, but next time I won't put so much effort
> into fixing up your work. Please learn how to submit patches
> properly.
>
> Thank you.
--- a/net/ipv4/ip_options.c.orig 2006-01-27 09:14:33.463612696 +0900
+++ b/net/ipv4/ip_options.c 2006-01-27 09:12:21.857619848 +0900
@@ -207,7 +207,7 @@
void ip_options_fragment(struct sk_buff * skb)
{
- unsigned char * optptr = skb->nh.raw;
+ unsigned char * optptr = skb->nh.raw + sizeof(struct iphdr);
struct ip_options * opt = &(IPCB(skb)->opt);
int l = opt->optlen;
int optlen;
next parent reply other threads:[~2006-05-08 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2006-05-08 5:39 ` [PATCH]ip_options_fragment() has no effect on fragmentation David S. Miller
2006-05-08 5:41 ` David S. Miller
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=200605051350.03300.weiyj@soft.fujitsu.com \
--to=weiyj@soft.fujitsu.com \
--cc=davem@davemloft.net \
--cc=netdev@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 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).