From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, gal@nvidia.com, leonro@nvidia.com,
gbayer@linux.ibm.com, yanjun.zhu@linux.dev, maxtram95@gmail.com
Subject: Re: [net 1/8] net/mlx5: Fix error path in multi-packet WQE transmit
Date: Thu, 03 Oct 2024 00:30:33 +0000 [thread overview]
Message-ID: <172791543351.1385485.12951789236369378613.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240925202013.45374-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Wed, 25 Sep 2024 13:20:06 -0700 you wrote:
> From: Gerd Bayer <gbayer@linux.ibm.com>
>
> Remove the erroneous unmap in case no DMA mapping was established
>
> The multi-packet WQE transmit code attempts to obtain a DMA mapping for
> the skb. This could fail, e.g. under memory pressure, when the IOMMU
> driver just can't allocate more memory for page tables. While the code
> tries to handle this in the path below the err_unmap label it erroneously
> unmaps one entry from the sq's FIFO list of active mappings. Since the
> current map attempt failed this unmap is removing some random DMA mapping
> that might still be required. If the PCI function now presents that IOVA,
> the IOMMU may assumes a rogue DMA access and e.g. on s390 puts the PCI
> function in error state.
>
> [...]
Here is the summary with links:
- [net,1/8] net/mlx5: Fix error path in multi-packet WQE transmit
https://git.kernel.org/netdev/net/c/2bcae12c795f
- [net,2/8] net/mlx5: Added cond_resched() to crdump collection
https://git.kernel.org/netdev/net/c/ec7931558941
- [net,3/8] net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()
https://git.kernel.org/netdev/net/c/f25389e77950
- [net,4/8] net/mlx5: Fix wrong reserved field in hca_cap_2 in mlx5_ifc
https://git.kernel.org/netdev/net/c/19da17010a55
- [net,5/8] net/mlx5: HWS, fixed double-free in error flow of creating SQ
https://git.kernel.org/netdev/net/c/d8c561741ef8
- [net,6/8] net/mlx5: HWS, changed E2BIG error to a negative return code
https://git.kernel.org/netdev/net/c/d15525f30010
- [net,7/8] net/mlx5e: SHAMPO, Fix overflow of hd_per_wq
https://git.kernel.org/netdev/net/c/023d2a43ed0d
- [net,8/8] net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice
https://git.kernel.org/netdev/net/c/7b124695db40
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:[~2024-10-03 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 20:20 [pull request][net 0/8] mlx5 fixes 2024-09-25 Saeed Mahameed
2024-09-25 20:20 ` [net 1/8] net/mlx5: Fix error path in multi-packet WQE transmit Saeed Mahameed
2024-10-03 0:30 ` patchwork-bot+netdevbpf [this message]
2024-09-25 20:20 ` [net 2/8] net/mlx5: Added cond_resched() to crdump collection Saeed Mahameed
2024-09-25 20:20 ` [net 3/8] net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() Saeed Mahameed
2024-09-25 20:20 ` [net 4/8] net/mlx5: Fix wrong reserved field in hca_cap_2 in mlx5_ifc Saeed Mahameed
2024-09-25 20:20 ` [net 5/8] net/mlx5: HWS, fixed double-free in error flow of creating SQ Saeed Mahameed
2024-09-25 20:20 ` [net 6/8] net/mlx5: HWS, changed E2BIG error to a negative return code Saeed Mahameed
2024-09-25 20:20 ` [net 7/8] net/mlx5e: SHAMPO, Fix overflow of hd_per_wq Saeed Mahameed
2024-09-25 20:20 ` [net 8/8] net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice Saeed Mahameed
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=172791543351.1385485.12951789236369378613.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=gbayer@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=maxtram95@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=yanjun.zhu@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.