From: patchwork-bot+netdevbpf@kernel•org
To: Taehee Yoo <ap420073@gmail•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, bpf@vger•kernel.org,
ecree.xilinx@gmail•com, habetsm.xilinx@gmail•com, ast@kernel•org,
daniel@iogearbox•net, hawk@kernel•org, john.fastabend@gmail•com,
cmclachlan@solarflare•com
Subject: Re: [PATCH net v2] net: sfc: add missing xdp queue reinitialization
Date: Fri, 01 Apr 2022 11:00:11 +0000 [thread overview]
Message-ID: <164881081193.13357.15286067348950686490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220330163703.25086-1-ap420073@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Wed, 30 Mar 2022 16:37:03 +0000 you wrote:
> After rx/tx ring buffer size is changed, kernel panic occurs when
> it acts XDP_TX or XDP_REDIRECT.
>
> When tx/rx ring buffer size is changed(ethtool -G), sfc driver
> reallocates and reinitializes rx and tx queues and their buffer
> (tx_queue->buffer).
> But it misses reinitializing xdp queues(efx->xdp_tx_queues).
> So, while it is acting XDP_TX or XDP_REDIRECT, it uses the uninitialized
> tx_queue->buffer.
>
> [...]
Here is the summary with links:
- [net,v2] net: sfc: add missing xdp queue reinitialization
https://git.kernel.org/netdev/net/c/059a47f1da93
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:[~2022-04-01 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 16:37 [PATCH net v2] net: sfc: add missing xdp queue reinitialization Taehee Yoo
2022-04-01 11:00 ` patchwork-bot+netdevbpf [this message]
2022-04-01 11:06 ` Martin Habets
2022-04-01 18:48 ` Taehee Yoo
2022-04-04 10:36 ` Martin Habets
2022-04-05 3:16 ` Taehee Yoo
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=164881081193.13357.15286067348950686490.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ap420073@gmail$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=cmclachlan@solarflare$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=habetsm.xilinx@gmail$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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