From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, daniel@iogearbox.net,
dsahern@kernel.org, yajun.deng@linux.dev, roopa@nvidia.com,
brauner@kernel.org, linux-kernel@vger.kernel.org, den@openvz.org,
kuznet@ms2.inr.ac.ru, khorenko@virtuozzo.com,
ptikhomirov@virtuozzo.com, andrey.zhadchenko@virtuozzo.com,
alexander@mihalicyn.com, kernel@openvz.org, devel@openvz.org
Subject: Re: [PATCH v3 0/2] neighbour: fix possible DoS due to net iface start/stop loop
Date: Mon, 15 Aug 2022 10:40:14 +0000 [thread overview]
Message-ID: <166056001417.15339.4238820299140401617.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220811152012.319641-1-alexander.mikhalitsyn@virtuozzo.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2022-08-15 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 10:35 [PATCH 0/2] neighbour: fix possible DoS due to net iface start/stop loop Alexander Mikhalitsyn
2022-07-29 10:35 ` [PATCH 1/2] neigh: " Alexander Mikhalitsyn
2022-08-01 15:08 ` David Ahern
2022-08-01 15:44 ` Denis V. Lunev
2022-07-29 10:35 ` [PATCH 2/2] neighbour: make proxy_queue.qlen limit per-device Alexander Mikhalitsyn
2022-08-10 16:08 ` [PATCH v2 0/2] neighbour: fix possible DoS due to net iface start/stop loop Alexander Mikhalitsyn
2022-08-10 16:08 ` [PATCH v2 1/2] neigh: " Alexander Mikhalitsyn
2022-08-15 9:44 ` Christian Brauner
2022-08-15 10:47 ` Denis V. Lunev
2022-08-10 16:08 ` [PATCH v2 2/2] neighbour: make proxy_queue.qlen limit per-device Alexander Mikhalitsyn
2022-08-11 14:46 ` [PATCH v2 0/2] neighbour: fix possible DoS due to net iface start/stop loop Jakub Kicinski
2022-08-11 14:51 ` Alexander Mikhalitsyn
2022-08-11 14:53 ` Jakub Kicinski
2022-08-11 14:57 ` Alexander Mikhalitsyn
2022-08-11 15:20 ` [PATCH v3 " Alexander Mikhalitsyn
2022-08-11 15:20 ` [PATCH v3 1/2] neigh: " Alexander Mikhalitsyn
2022-08-11 15:20 ` [PATCH v3 2/2] neighbour: make proxy_queue.qlen limit per-device Alexander Mikhalitsyn
2022-08-15 10:40 ` patchwork-bot+netdevbpf [this message]
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=166056001417.15339.4238820299140401617.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=alexander@mihalicyn.com \
--cc=andrey.zhadchenko@virtuozzo.com \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=roopa@nvidia.com \
--cc=yajun.deng@linux.dev \
/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.