[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1489025457.28631.19.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Wed, 08 Mar 2017 18:10:57 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jon Maxwell <jmaxwell37@...il.com>
Cc: gerrit@....abdn.ac.uk, davem@...emloft.net, edumazet@...gle.com,
andreyknvl@...gle.com, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net, ncardwell@...gle.com,
dccp@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, jmaxwell@...hat.com,
Eric Garver <egarver@...hat.com>,
Hannes Sowa <hsowa@...hat.com>
Subject: Re: [PATCH net] dccp/tcp: fix routing redirect race
On Thu, 2017-03-09 at 12:15 +1100, Jon Maxwell wrote:
> We have seen a few incidents lately where a dst_enty has been freed
> with a dangling TCP socket reference (sk->sk_dst_cache) pointing to that
> dst_entry. If the conditions/timings are right a crash then ensues when the
> freed dst_entry is referenced later on. A Common crashing back trace is:
Very nice catch !
Don't we have a similar issue for IPv6 ?
Powered by blists - more mailing lists