[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89i+CTAYZft=LT+ZH8bg__9p63URnQH=s9=AL7MO4rbvPJg@mail.gmail.com>
Date: Thu, 7 Dec 2023 21:04:57 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: thinker.li@...il.com
Cc: netdev@...r.kernel.org, martin.lau@...ux.dev, kernel-team@...a.com,
davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, dsahern@...nel.org,
sinquersw@...il.com, kuifeng@...a.com
Subject: Re: [PATCH bpf-next] ipv6: fix warning messages in fib6_info_release().
On Thu, Dec 7, 2023 at 8:50 PM <thinker.li@...il.com> wrote:
>
> From: Kui-Feng Lee <thinker.li@...il.com>
>
> The previous patch doesn't handle the case in ip6_route_info_create().
> Move calling to fib6_set_expires_locked() to the end of the function to
> avoid the false alarm of the previous patch.
>
> Fixes: 5a08d0065a91 ("ipv6: add debug checks in fib6_info_release()")
This looks quite wrong.
Let's separate things to have clean stable backports.
I will submit my single liner, you will submit a patch fixing your prior commit,
otherwise linux-6.6 and linux-6.7 will still have a bug.
Powered by blists - more mailing lists