netdev - Re: [PATCH] net: bridge: vlan: fix memory leak in __allowed

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: <164330340982.19448.11235674242390336417.git-patchwork-notify@kernel.org>
Date:   Thu, 27 Jan 2022 17:10:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Tim Yi <tim.yi@...a8.com>
Cc:     nikolay@...dia.com, roopa@...dia.com, davem@...emloft.net,
        kuba@...nel.org, bridge@...ts.linux-foundation.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH] net: bridge: vlan: fix memory leak in __allowed_ingress

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Thu, 27 Jan 2022 15:49:53 +0800 you wrote:
> When using per-vlan state, if vlan snooping and stats are disabled,
> untagged or priority-tagged ingress frame will go to check pvid state.
> If the port state is forwarding and the pvid state is not
> learning/forwarding, untagged or priority-tagged frame will be dropped
> but skb memory is not freed.
> Should free skb when __allowed_ingress returns false.
> 
> [...]

Here is the summary with links:
  - net: bridge: vlan: fix memory leak in __allowed_ingress
    https://git.kernel.org/netdev/net/c/fd20d9738395

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html