From: Kui-Feng Lee <sinquersw@gmail.com>
To: David Ahern <dsahern@kernel.org>, netdev@vger.kernel.org
Cc: edumazet@google.com, Kui-Feng Lee <thinker.li@gmail.com>
Subject: Re: [PATCH net] net/ipv6: Revert remove expired routes with a separated list of routes
Date: Mon, 18 Dec 2023 18:45:03 -0800 [thread overview]
Message-ID: <9e8f86e1-8663-4bbb-baa9-fe0030dbbabd@gmail.com> (raw)
In-Reply-To: <c3ae9c3a-9ecd-4b22-a908-9da587c1c88b@kernel.org>
On 12/18/23 18:38, David Ahern wrote:
> On 12/18/23 6:14 PM, Kui-Feng Lee wrote:
>>
>>
>> On 12/17/23 10:55, David Ahern wrote:
>>> Revert the remainder of 5a08d0065a915 which added a warn on if a fib
>>> entry is still on the gc_link list, and then revert all of the commit
>>> in the Fixes tag. The commit has some race conditions given how expires
>>> is managed on a fib6_info in relation to timer start, adding the entry
>>> to the gc list and setting the timer value leading to UAF. Revert
>>> the commit and try again in a later release.
>>
>> May I know what your concerns are about the patch I provided?
>> Even I try it again later, I still need to know what I miss and should
>> address.
>
> This is a judgement call based on 6.7-rc number and upcoming holidays
> with people offline. A bug fix is needed for a performance optimization;
> the smart response here is to revert the patch and try again after the
> holidays.
Got it! Thanks!
next prev parent reply other threads:[~2023-12-19 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 18:55 [PATCH net] net/ipv6: Revert remove expired routes with a separated list of routes David Ahern
2023-12-18 16:31 ` Eric Dumazet
2023-12-19 1:14 ` Kui-Feng Lee
2023-12-19 2:38 ` David Ahern
2023-12-19 2:45 ` Kui-Feng Lee [this message]
2023-12-19 3:22 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e8f86e1-8663-4bbb-baa9-fe0030dbbabd@gmail.com \
--to=sinquersw@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=thinker.li@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.