From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, dsahern@gmail.com,
jiri@resnulli.us
Subject: Re: [PATCH net-next 0/2] net: control the length of the altname list
Date: Fri, 11 Mar 2022 04:30:13 +0000 [thread overview]
Message-ID: <164697301316.12732.15946977817982589075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309182914.423834-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Mar 2022 10:29:12 -0800 you wrote:
> Count the memory used for altnames and don't let user
> overflow the property nlattr. This was reported by George:
> https://lore.kernel.org/all/3e564baf-a1dd-122e-2882-ff143f7eb578@gmail.com/
>
> Targeting net-next because I think we generally don't consider
> tightening "root controlled" memory accounting to be a fix.
> There's also some risk of breakage.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: account alternate interface name memory
https://git.kernel.org/netdev/net-next/c/5d26cff5bdbe
- [net-next,2/2] net: limit altnames to 64k total
https://git.kernel.org/netdev/net-next/c/155fb43b70b5
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-03-11 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 18:29 [PATCH net-next 0/2] net: control the length of the altname list Jakub Kicinski
2022-03-09 18:29 ` [PATCH net-next 1/2] net: account alternate interface name memory Jakub Kicinski
2022-03-09 18:29 ` [PATCH net-next 2/2] net: limit altnames to 64k total Jakub Kicinski
2022-03-10 2:51 ` David Ahern
2022-03-10 3:37 ` Jakub Kicinski
2022-03-10 3:50 ` David Ahern
2022-03-11 4:30 ` 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=164697301316.12732.15946977817982589075.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).