From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: krishneil.k.singh@intel.com, alan.brady@intel.com,
aleksander.lobakin@intel.com, andrew+netdev@lunn.ch,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net] idpf: fix mismatched free function for dma_alloc_coherent
Date: Tue, 30 Sep 2025 01:20:06 +0000 [thread overview]
Message-ID: <175919520650.1775912.18298480194325200871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250925180212.415093-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 25 Sep 2025 11:02:10 -0700 you wrote:
> The mailbox receive path allocates coherent DMA memory with
> dma_alloc_coherent(), but frees it with dmam_free_coherent().
> This is incorrect since dmam_free_coherent() is only valid for
> buffers allocated with dmam_alloc_coherent().
>
> Fix the mismatch by using dma_free_coherent() instead of
> dmam_free_coherent
>
> [...]
Here is the summary with links:
- [net] idpf: fix mismatched free function for dma_alloc_coherent
https://git.kernel.org/netdev/net/c/b9bd25f47eb7
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:[~2025-09-30 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 18:02 [PATCH net] idpf: fix mismatched free function for dma_alloc_coherent Alok Tiwari
2025-09-26 14:03 ` Simon Horman
2025-09-29 6:28 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-09-29 22:53 ` Jacob Keller
2025-09-29 23:07 ` Chittim, Madhu
2025-09-30 1: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=175919520650.1775912.18298480194325200871.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.brady@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=krishneil.k.singh@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).