[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166056001417.15339.4238820299140401617.git-patchwork-notify@kernel.org>
Date: Mon, 15 Aug 2022 10:40:14 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@...tuozzo.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, daniel@...earbox.net,
dsahern@...nel.org, yajun.deng@...ux.dev, roopa@...dia.com,
brauner@...nel.org, linux-kernel@...r.kernel.org, den@...nvz.org,
kuznet@....inr.ac.ru, khorenko@...tuozzo.com,
ptikhomirov@...tuozzo.com, andrey.zhadchenko@...tuozzo.com,
alexander@...alicyn.com, kernel@...nvz.org, devel@...nvz.org
Subject: Re: [PATCH v3 0/2] neighbour: fix possible DoS due to net iface
start/stop loop
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:
On Thu, 11 Aug 2022 18:20:10 +0300 you wrote:
> Dear friends,
>
> Recently one of OpenVZ users reported that they have issues with network
> availability of some containers. It was discovered that the reason is absence
> of ARP replies from the Host Node on the requests about container IPs.
>
> Of course, we started from tcpdump analysis and noticed that ARP requests
> successfuly comes to the problematic node external interface. So, something
> was wrong from the kernel side.
>
> [...]
Here is the summary with links:
- [v3,1/2] neigh: fix possible DoS due to net iface start/stop loop
https://git.kernel.org/netdev/net/c/66ba215cb513
- [v3,2/2] neighbour: make proxy_queue.qlen limit per-device
https://git.kernel.org/netdev/net/c/0ff4eb3d5ebb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists