From: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
Cc: edumazet@google.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org
Subject: Re: [PATCH net v3] net: sched: cls_u32: Fix u32's systematic failure to free IDR entries for hnodes.
Date: Thu, 7 Nov 2024 23:58:02 +0100 [thread overview]
Message-ID: <7c4dc799-ebf6-47fe-a25f-bb84d6faa0cf@orange.com> (raw)
In-Reply-To: <CAM0EoMknpWa-GapPyWZzXhzaDe6xBb7rtOovTk6Dpd2X=acknA@mail.gmail.com>
On 07/11/2024 15:47, Jamal Hadi Salim wrote:
> On Thu, Nov 7, 2024 at 9:45 AM Jamal Hadi Salim <jhs@mojatatu.com> wrote:
>>
>> Hi,
>>
>> On Wed, Nov 6, 2024 at 9:32 AM Alexandre Ferrieux
>> <alexandre.ferrieux@gmail.com> wrote:
>> >
>> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>> > Signed-off-by: Alexandre Ferrieux <alexandre.ferrieux@orange.com>
>>
>> I'd like to take a closer look at this - just tied up with something
>> at the moment. Give me a day or so.
>> Did you run tdc tests after your patch?
>
> Also, for hero status points, consider submitting a tdc test case.
Hi Jamal, thanks for looking into this.
Just posted a v4 with a tdc test case.
Of course, I also verified that "tdc -c u32" has no regression :)
next prev parent reply other threads:[~2024-11-07 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 14:32 [PATCH net v3] net: sched: cls_u32: Fix u32's systematic failure to free IDR entries for hnodes Alexandre Ferrieux
2024-11-07 14:45 ` Jamal Hadi Salim
2024-11-07 14:47 ` Jamal Hadi Salim
2024-11-07 22:58 ` Alexandre Ferrieux [this message]
2024-11-07 23:14 ` Alexandre Ferrieux
2024-11-09 13:07 ` Jamal Hadi Salim
2024-11-09 18:59 ` Alexandre Ferrieux
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=7c4dc799-ebf6-47fe-a25f-bb84d6faa0cf@orange.com \
--to=alexandre.ferrieux@gmail.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@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.