From: patchwork-bot+netdevbpf@kernel.org
To: Manish Chopra <manishc@marvell.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, aelior@marvell.com,
palok@marvell.com, njavali@marvell.com, skashyap@marvell.com,
jmeneghi@redhat.com, pabeni@redhat.com, cleech@redhat.com,
edumazet@google.com, horms@kernel.org,
Yuval.Mintz@caviumnetworks.com, Ram.Amrani@caviumnetworks.com,
davem@davemloft.net
Subject: Re: [PATCH net] qed: fix LL2 RX buffer allocation
Date: Sun, 15 Oct 2023 13:30:23 +0000 [thread overview]
Message-ID: <169737662319.24568.4521440160238409297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231013131812.873331-1-manishc@marvell.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 13 Oct 2023 18:48:12 +0530 you wrote:
> Driver allocates the LL2 rx buffers from kmalloc()
> area to construct the skb using slab_build_skb()
>
> The required size allocation seems to have overlooked
> for accounting both skb_shared_info size and device
> placement padding bytes which results into the below
> panic when doing skb_put() for a standard MTU sized frame.
>
> [...]
Here is the summary with links:
- [net] qed: fix LL2 RX buffer allocation
https://git.kernel.org/netdev/net/c/2f3389c73832
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-10-15 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 13:18 [PATCH net] qed: fix LL2 RX buffer allocation Manish Chopra
2023-10-15 13:30 ` patchwork-bot+netdevbpf [this message]
2023-10-16 16:17 ` Chris Leech
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=169737662319.24568.4521440160238409297.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ram.Amrani@caviumnetworks.com \
--cc=Yuval.Mintz@caviumnetworks.com \
--cc=aelior@marvell.com \
--cc=cleech@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jmeneghi@redhat.com \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=njavali@marvell.com \
--cc=pabeni@redhat.com \
--cc=palok@marvell.com \
--cc=skashyap@marvell.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;
as well as URLs for NNTP newsgroup(s).