[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <163283100725.29415.17214439381941428620.git-patchwork-notify@kernel.org>
Date: Tue, 28 Sep 2021 12:10:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: MichelleJin <shjy180909@...il.com>
Cc: davem@...emloft.net, kuba@...nel.org, yoshfuji@...ux-ipv6.org,
dsahern@...nel.org, johannes@...solutions.net, saeedm@...dia.com,
leon@...nel.org, roid@...dia.com, paulb@...dia.com,
ozsh@...dia.com, lariel@...dia.com, cmi@...dia.com,
netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/3] check return value of rhashtable_init in
mlx5e, ipv6, mac80211
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 27 Sep 2021 03:34:54 +0000 you wrote:
> When rhashtable_init() fails, it returns -EINVAL.
> However, since error return value of rhashtable_init is not checked,
> it can cause use of uninitialized pointers.
> So, fix unhandled errors of rhashtable_init.
> The three patches are essentially the same logic.
>
> v1->v2:
> - change commit message
> - fix possible memory leaks
> v2->v3:
> - split patch into mlx5e, ipv6, mac80211
> v3->v4:
> - fix newly created warnings due to patches in net/ipv6/seg6.c
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] net/mlx5e: check return value of rhashtable_init
https://git.kernel.org/netdev/net-next/c/d7cade513752
- [net-next,v4,2/3] net: ipv6: check return value of rhashtable_init
https://git.kernel.org/netdev/net-next/c/f04ed7d277e8
- [net-next,v4,3/3] net: mac80211: check return value of rhashtable_init
https://git.kernel.org/netdev/net-next/c/f43bed7193a3
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