From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] inet6: Fix paramater issue of inet6_csk_xmit
Date: Fri, 01 Aug 2008 13:17:15 +0800 [thread overview]
Message-ID: <48929C5B.5030108@cn.fujitsu.com> (raw)
In-Reply-To: <20080731.204826.189988398.davem@davemloft.net>
David Miller wrote:
> From: Wei Yongjun <yjwei@cn.fujitsu.com>
> Date: Thu, 31 Jul 2008 17:56:25 +0800
>
>
>> inet6_csk_xmit() has a paramater ipfragok, but never pass to
>> ip6_xmit(), always call it with ipfragok = 0.
>>
>> This patch fixed this problem by instead 0 of ipfragok.
>>
>> Compiled test only.
>>
>> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
>>
>
> I would like to see someone do some testing of this patch
> before I apply it.
>
inet6_csk_xmit() just be used by tcp and dccp:
1042 net/dccp/ipv6.c .queue_xmit = inet6_csk_xmit
1853 net/ipv6/tcp_ipv6.c .queue_xmit = inet6_csk_xmit,
And used always with ipfragok = 0.
139 net/dccp/output.c err = icsk->icsk_af_ops->queue_xmit(skb, 0);
626 net/ipv4/tcp_output.c err = icsk->icsk_af_ops->queue_xmit(skb, 0);
I can not find any place used inet6_csk_xmit() with ipfragok = 1.
So I think it is safe to apply this patch. Or maybe this paramater is
useless.
next prev parent reply other threads:[~2008-08-01 5:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 9:56 [PATCH] inet6: Fix paramater issue of inet6_csk_xmit Wei Yongjun
2008-08-01 3:48 ` David Miller
2008-08-01 5:17 ` Wei Yongjun [this message]
2008-08-01 9:11 ` Herbert Xu
2008-08-01 9:18 ` David Miller
2008-08-01 9:25 ` Herbert Xu
2008-08-01 11:50 ` Herbert Xu
2008-08-01 13:14 ` Herbert Xu
2008-08-01 14:50 ` Vlad Yasevich
2008-08-02 0:30 ` Herbert Xu
2008-08-02 23:26 ` Vlad Yasevich
2008-08-03 2:01 ` Herbert Xu
2008-08-03 6:56 ` David Miller
2008-08-04 1:03 ` Vlad Yasevich
2008-08-04 1:55 ` Herbert Xu
2008-08-04 2:58 ` Wei Yongjun
2008-08-04 3:05 ` Herbert Xu
2008-08-04 4:16 ` David Miller
2008-08-04 4:15 ` David 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=48929C5B.5030108@cn.fujitsu.com \
--to=yjwei@cn.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).