Re: A bug in udp6_input() - should use proto instead of ip6->ip6_nxt

2015-08-31 Thread Tiwei Bie
On Mon, Aug 31, 2015 at 09:28:07AM +, Bjoern A. Zeeb wrote: > > > On 31 Aug 2015, at 04:05 , Tiwei Bie wrote: > > > > I found a bug in udp6_input(). The 'proto' parameter should be used to > > get the protocol number (UDP or UDPLITE), instead of ip6->ip6_nxt. > > > > Because ip6->ip6_nxt ma

Re: A bug in udp6_input() - should use proto instead of ip6->ip6_nxt

2015-08-31 Thread Bjoern A. Zeeb
> On 31 Aug 2015, at 04:05 , Tiwei Bie wrote: > > I found a bug in udp6_input(). The 'proto' parameter should be used to > get the protocol number (UDP or UDPLITE), instead of ip6->ip6_nxt. > > Because ip6->ip6_nxt may be the protocol number of extension header, > such as: > > If a UDP packet

A bug in udp6_input() - should use proto instead of ip6->ip6_nxt

2015-08-30 Thread Tiwei Bie
I found a bug in udp6_input(). The 'proto' parameter should be used to get the protocol number (UDP or UDPLITE), instead of ip6->ip6_nxt. Because ip6->ip6_nxt may be the protocol number of extension header, such as: If a UDP packet is an "atomic" fragment, frag6_input() will return directly, and