[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c86e9056-151c-6b9d-9475-99158de0874b@cumulusnetworks.com>
Date: Tue, 25 Apr 2017 09:54:04 -0600
From: David Ahern <dsa@...ulusnetworks.com>
To: Andrey Konovalov <andreyknvl@...gle.com>
Cc: netdev <netdev@...r.kernel.org>,
Dmitry Vyukov <dvyukov@...gle.com>, mmanning@...cade.com,
Martin KaFai Lau <kafai@...com>
Subject: Re: [PATCH v3 net] net: ipv6: regenerate host route if moved to gc
list
On 4/25/17 6:50 AM, Andrey Konovalov wrote:
> I've been running syzkaller with your patch and got another report
> from ip6_pol_route.
In general the existing patch cleans up all of the ipv6 fib kasan and
WARN_ON traces that were seen?
>
> It happened only once so far and I couldn't reproduce it.
Some similarity in the sense of a ipv4 route in the ipv6 fib. That's
only going to happen if it hits the dst gc list and then back.
This duplicates what Dmitry reported on March 3rd.
Powered by blists - more mailing lists