From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next V2] net: introduce skb_poison_list and use in kfree_skb_list
Date: Mon, 06 Feb 2023 10:00:16 +0000 [thread overview]
Message-ID: <167567761656.25195.16301728164675048555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <167542916933.1167230.1244118780145312645.stgit@firesoul>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2023-02-06 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:59 [PATCH net-next V2] net: introduce skb_poison_list and use in kfree_skb_list Jesper Dangaard Brouer
2023-02-06 10:00 ` 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=167567761656.25195.16301728164675048555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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