[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190124.182541.341610576126108739.davem@davemloft.net>
Date: Thu, 24 Jan 2019 18:25:41 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: lucien.xin@...il.com
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-sctp@...r.kernel.org, marcelo.leitner@...il.com,
nhorman@...driver.com
Subject: Re: [PATCH net] sctp: set flow sport from saddr only when it's 0
From: Xin Long <lucien.xin@...il.com>
Date: Tue, 22 Jan 2019 02:42:41 +0800
> Now sctp_transport_pmtu() passes transport->saddr into .get_dst() to set
> flow sport from 'saddr'. However, transport->saddr is set only when
> transport->dst exists in sctp_transport_route().
>
> If sctp_transport_pmtu() is called without transport->saddr set, like
> when transport->dst doesn't exists, the flow sport will be set to 0
> from transport->saddr, which will cause a wrong route to be got.
>
> Commit 6e91b578bf3f ("sctp: re-use sctp_transport_pmtu in
> sctp_transport_route") made the issue be triggered more easily
> since sctp_transport_pmtu() would be called in sctp_transport_route()
> after that.
>
> In gerneral, fl4->fl4_sport should always be set to
> htons(asoc->base.bind_addr.port), unless transport->asoc doesn't exist
> in sctp_v4/6_get_dst(), which is the case:
>
> sctp_ootb_pkt_new() ->
> sctp_transport_route()
>
> For that, we can simply handle it by setting flow sport from saddr only
> when it's 0 in sctp_v4/6_get_dst().
>
> Fixes: 6e91b578bf3f ("sctp: re-use sctp_transport_pmtu in sctp_transport_route")
> Reported-by: Ying Xu <yinxu@...hat.com>
> Signed-off-by: Xin Long <lucien.xin@...il.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists