From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, Thomas Voegtle <tv@lio96.de>,
aelior@marvell.com, skalluru@marvell.com, manishc@marvell.com,
keescook@chromium.org
Subject: Re: [PATCH net] bnx2x: use the right build_skb() helper
Date: Wed, 29 Mar 2023 15:35:33 +0300 [thread overview]
Message-ID: <20230329123533.GU831478@unreal> (raw)
In-Reply-To: <20230329000013.2734957-1-kuba@kernel.org>
On Tue, Mar 28, 2023 at 05:00:13PM -0700, Jakub Kicinski wrote:
> build_skb() no longer accepts slab buffers. Since slab use is fairly
> uncommon we prefer the drivers to call a separate slab_build_skb()
> function appropriately.
>
> bnx2x uses the old semantics where size of 0 meant buffer from slab.
> It sets the fp->rx_frag_size to 0 for MTUs which don't fit in a page.
> It needs to call slab_build_skb().
>
> This fixes the WARN_ONCE() of incorrect API use seen with bnx2x.
>
> Reported-by: Thomas Voegtle <tv@lio96.de>
> Link: https://lore.kernel.org/all/b8f295e4-ba57-8bfb-7d9c-9d62a498a727@lio96.de/
> Fixes: ce098da1497c ("skbuff: Introduce slab_build_skb()")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: aelior@marvell.com
> CC: skalluru@marvell.com
> CC: manishc@marvell.com
> CC: keescook@chromium.org
> ---
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2023-03-29 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 0:00 [PATCH net] bnx2x: use the right build_skb() helper Jakub Kicinski
2023-03-29 12:35 ` Leon Romanovsky [this message]
2023-03-30 4:40 ` patchwork-bot+netdevbpf
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=20230329123533.GU831478@unreal \
--to=leon@kernel.org \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skalluru@marvell.com \
--cc=tv@lio96.de \
/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).