netdev - Re: [PATCH net-next V2] net: introduce skb_poison_list and use in kfree_skb

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: <167567761656.25195.16301728164675048555.git-patchwork-notify@kernel.org>
Date:   Mon, 06 Feb 2023 10:00:16 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jesper Dangaard Brouer <brouer@...hat.com>
Cc:     netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
        edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net-next V2] net: introduce skb_poison_list and use in
 kfree_skb_list

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Fri, 03 Feb 2023 13:59:29 +0100 you wrote:
> First user of skb_poison_list is in kfree_skb_list_reason, to catch bugs
> earlier like introduced in commit eedade12f4cb ("net: kfree_skb_list use
> kmem_cache_free_bulk"). For completeness mentioned bug have been fixed in
> commit f72ff8b81ebc ("net: fix kfree_skb_list use of skb_mark_not_on_list").
> 
> In case of a bug like mentioned commit we would have seen OOPS with:
>  general protection fault, probably for non-canonical address 0xdead000000000870
> And content of one the registers e.g. R13: dead000000000800
> 
> [...]

Here is the summary with links:
  - [net-next,V2] net: introduce skb_poison_list and use in kfree_skb_list
    https://git.kernel.org/netdev/net-next/c/9dde0cd3b10f

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