[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJWo8U=csnZNh+QHh7Sf8+Gaig56-HU9BbZbGeeFs5g3w@mail.gmail.com>
Date: Mon, 25 Sep 2017 19:23:58 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Martin KaFai Lau <kafai@...com>
Cc: Wei Wang <weiwan@...gle.com>, David Miller <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH net] ipv6: remove incorrect WARN_ON() in fib6_del()
On Mon, Sep 25, 2017 at 7:07 PM, Martin KaFai Lau <kafai@...com> wrote:
> I am probably still missing something.
>
> Considering the del operation should be under the writer lock,
> if rt->rt6i_node should be NULL (for rt that has already been
> removed from fib6), why this WARN_ON() is triggered?
>
> An example may help.
>
Look at the stack trace, you'll find the answers...
ip6_link_failure() -> ip6_del_rt()
Note that rt might have been deleted from the _tree_ already.
Powered by blists - more mailing lists