linux-kernel - Re: [PATCH net-next v2] net: switch to storing KCOV handle directly in sk

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]

Date:   Tue, 01 Dec 2020 21:00:06 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Marco Elver <elver@...gle.com>
Cc:     kuba@...nel.org, davem@...emloft.net, johannes@...solutions.net,
        a.nogikh@...il.com, andreyknvl@...gle.com, dvyukov@...gle.com,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        linux-wireless@...r.kernel.org, idosch@...sch.org, fw@...len.de,
        willemb@...gle.com
Subject: Re: [PATCH net-next v2] net: switch to storing KCOV handle directly in
 sk_buff

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Wed, 25 Nov 2020 23:48:40 +0100 you wrote:
> It turns out that usage of skb extensions can cause memory leaks. Ido
> Schimmel reported: "[...] there are instances that blindly overwrite
> 'skb->extensions' by invoking skb_copy_header() after __alloc_skb()."
> 
> Therefore, give up on using skb extensions for KCOV handle, and instead
> directly store kcov_handle in sk_buff.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: switch to storing KCOV handle directly in sk_buff
    https://git.kernel.org/netdev/net-next/c/fa69ee5aa48b

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