From: patchwork-bot+netdevbpf@kernel.org
To: Brett Creeley <brett.creeley@amd.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
alvaro.karsz@solid-run.com, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net,
xuanzhuo@linux.alibaba.com, jasowang@redhat.com, mst@redhat.com,
shannon.nelson@amd.com, allen.hubbe@amd.com
Subject: Re: [PATCH net] virtio_net: use control_buf for coalesce params
Date: Wed, 07 Jun 2023 04:20:22 +0000 [thread overview]
Message-ID: <168611162271.32150.1707955265186129057.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230605195925.51625-1-brett.creeley@amd.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Jun 2023 12:59:25 -0700 you wrote:
> Commit 699b045a8e43 ("net: virtio_net: notifications coalescing
> support") added coalescing command support for virtio_net. However,
> the coalesce commands are using buffers on the stack, which is causing
> the device to see DMA errors. There should also be a complaint from
> check_for_stack() in debug_dma_map_xyz(). Fix this by adding and using
> coalesce params from the control_buf struct, which aligns with other
> commands.
>
> [...]
Here is the summary with links:
- [net] virtio_net: use control_buf for coalesce params
https://git.kernel.org/netdev/net/c/accc1bf23068
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-06-07 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 19:59 [PATCH net] virtio_net: use control_buf for coalesce params Brett Creeley
2023-06-06 1:44 ` Jason Wang
2023-06-06 1:50 ` Xuan Zhuo
2023-06-06 8:29 ` Michael S. Tsirkin
2023-06-07 4:20 ` 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=168611162271.32150.1707955265186129057.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=allen.hubbe@amd.com \
--cc=alvaro.karsz@solid-run.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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