linux-kernel - Re: hard-coded limit on unresolved multicast route cache in ipv4/ipmr.c causes slow, unreliable creation of multicast routes on busy networks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20190625.130350.859562313660296893.davem@davemloft.net>
Date:   Tue, 25 Jun 2019 13:03:50 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     liuhangbin@...il.com
Cc:     sukumarg1973@...il.com, karn@...q.net, kuznet@....inr.ac.ru,
        yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: hard-coded limit on unresolved multicast route cache in
 ipv4/ipmr.c causes slow, unreliable creation of multicast routes on busy
 networks

From: Hangbin Liu <liuhangbin@...il.com>
Date: Tue, 25 Jun 2019 14:15:07 +0800

> On Tue, Dec 18, 2018 at 09:55:45PM -0800, David Miller wrote:
>> From: Sukumar Gopalakrishnan <sukumarg1973@...il.com>
>> Date: Wed, 19 Dec 2018 10:57:02 +0530
>> 
>> > Hi David,
>> > 
>> >   There are two patch for this issue:
>> >    1) Your changes which removes cache_resolve_queue_len
>> >     2) Hangbin's changes which make cache_resolve_queue_len configurable.
>> > 
>> > Which one will be chosen for this issue ?
>> 
>> I do plan to look into this, sorry for taking so long.
>> 
>> Right now I am overwhelmed preparing for the next merge window and
>> synchronizing with other developers for that.
>> 
>> Please be patient.
> 
> Hi David,
> 
> Any progress for this issue?

I have absolutely no context from a discussion that happened back in Dec 2018

If it is important to you, please restart the discussion with a new mailing list
posting restating the problem from the beginning and reiterating all of the
points and arguments that have been made thus far.