Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-27 Thread David Miller
From: Xufeng Zhang Date: Fri, 25 Apr 2014 16:55:41 +0800 > commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is > in output route lookups.) introduces another regression which > is very similar to the problem of commit e6b45241c (ipv4: reset > flowi parameters on route connect) wants to

Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-27 Thread David Miller
From: Xufeng Zhang xufeng.zh...@windriver.com Date: Fri, 25 Apr 2014 16:55:41 +0800 commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is in output route lookups.) introduces another regression which is very similar to the problem of commit e6b45241c (ipv4: reset flowi parameters on

Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Vlad Yasevich
On 04/25/2014 04:55 AM, Xufeng Zhang wrote: > commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is > in output route lookups.) introduces another regression which > is very similar to the problem of commit e6b45241c (ipv4: reset > flowi parameters on route connect) wants to fix: > Before we

Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Greg KH
On Fri, Apr 25, 2014 at 04:55:41PM +0800, Xufeng Zhang wrote: > commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is > in output route lookups.) introduces another regression which > is very similar to the problem of commit e6b45241c (ipv4: reset > flowi parameters on route connect) wants

[PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Xufeng Zhang
commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is in output route lookups.) introduces another regression which is very similar to the problem of commit e6b45241c (ipv4: reset flowi parameters on route connect) wants to fix: Before we call ip_route_output_key() in sctp_v4_get_dst() to

[PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Xufeng Zhang
commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is in output route lookups.) introduces another regression which is very similar to the problem of commit e6b45241c (ipv4: reset flowi parameters on route connect) wants to fix: Before we call ip_route_output_key() in sctp_v4_get_dst() to

Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Greg KH
On Fri, Apr 25, 2014 at 04:55:41PM +0800, Xufeng Zhang wrote: commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is in output route lookups.) introduces another regression which is very similar to the problem of commit e6b45241c (ipv4: reset flowi parameters on route connect) wants to

Re: [PATCH V2] sctp: reset flowi4_oif parameter on route lookup

2014-04-25 Thread Vlad Yasevich
On 04/25/2014 04:55 AM, Xufeng Zhang wrote: commit 813b3b5db83 (ipv4: Use caller's on-stack flowi as-is in output route lookups.) introduces another regression which is very similar to the problem of commit e6b45241c (ipv4: reset flowi parameters on route connect) wants to fix: Before we call