Re: ip_icmp reference fix

2016-08-22 Thread Claudio Jeker
On Mon, Aug 22, 2016 at 01:21:47PM +0200, Martin Pieuchot wrote: > When it comes to reference counting in the receiving path, route entries > act as proxy for interface addresses. In other words you CANNOT > dereference ``rt->rt_ifa'' after calling rtfree(9). > > Diff below fixes that in

Re: ip_icmp reference fix

2016-08-22 Thread Alexander Bluhm
On Mon, Aug 22, 2016 at 01:21:47PM +0200, Martin Pieuchot wrote: > When it comes to reference counting in the receiving path, route entries > act as proxy for interface addresses. In other words you CANNOT > dereference ``rt->rt_ifa'' after calling rtfree(9). > > Diff below fixes that in

Re: ip_icmp reference fix

2016-08-22 Thread Jeremie Courreges-Anglas
Martin Pieuchot writes: > When it comes to reference counting in the receiving path, route entries > act as proxy for interface addresses. In other words you CANNOT > dereference ``rt->rt_ifa'' after calling rtfree(9). > > Diff below fixes that in icmp_reflect(), ok? ok jca@

ip_icmp reference fix

2016-08-22 Thread Martin Pieuchot
When it comes to reference counting in the receiving path, route entries act as proxy for interface addresses. In other words you CANNOT dereference ``rt->rt_ifa'' after calling rtfree(9). Diff below fixes that in icmp_reflect(), ok? Index: netmpls/mpls_input.c