From: Patrick McHardy <kaber@trash.net>
To: yoshfuji@linux-ipv6.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [XFRM]: Fix ICMP tempsel
Date: Sun, 20 Feb 2005 08:13:28 +0100 [thread overview]
Message-ID: <42183898.7020607@trash.net> (raw)
In-Reply-To: <20050220.155527.54695259.yoshfuji@linux-ipv6.org>
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[ wrote:
> I didn't this because there are several places which depend on u8.
> If we go this way, we need to fix other places as well. e.g.
>
> net/ipv4/raw.c:raw_probe_proto_opt()
get_user(fl->fl_icmp_type, type);
__get_user(fl->fl_icmp_code, code);
On x86_64 both care only about the pointer type, not the target type.
> net/ipv4/xfrm4_policy.c:_decode_session4()
u8 *icmp = xprth;
fl->fl_icmp_type = icmp[0];
fl->fl_icmp_code = icmp[1];
No problem here.
> net/ipv6/raw.c:rawv6_probe_proto_opt()
Same as IPv4.
> net/ipv6/netfilter/ip6t_REJECT.c:send_unreach()
Not in mainline :)
> net/ipv6/xfrm6_policy.c:_decode_session6()
Same as IPv4.
> net/ipv6/ndisc.c:ndisc_flow_init()
fl->fl_icmp_type = type;
fl->fl_icmp_code = 0;
No problem.
> net/ipv6/icmp.c:icmpv6_send()
fl.fl_icmp_type = type;
fl.fl_icmp_code = code;
Also ok.
> net/ipv6/icmp.c:icmpv6_echo_reply()
fl.fl_icmp_type = ICMPV6_ECHO_REPLY;
Same here.
>
> (Note that type and code are stored in network-byte order.)
Both are u8 so there is no byte order.
Regards
Patrick
next prev parent reply other threads:[~2005-02-20 7:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 11:43 [XFRM]: Fix ICMP tempsel Patrick McHardy
2005-02-19 12:23 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-19 18:43 ` Herbert Xu
2005-02-19 18:55 ` Patrick McHardy
2005-02-20 5:30 ` Patrick McHardy
2005-02-20 6:55 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-20 7:13 ` Patrick McHardy [this message]
2005-02-20 7:37 ` Herbert Xu
2005-02-20 8:35 ` Patrick McHardy
2005-02-20 8:58 ` YOSHIFUJI Hideaki
2005-02-20 11:12 ` Herbert Xu
2005-02-20 11:20 ` Patrick McHardy
2005-02-20 12:00 ` YOSHIFUJI Hideaki / 吉藤英明
2005-03-10 4:49 ` 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=42183898.7020607@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).