From: patchwork-bot+netdevbpf@kernel.org
To: Gerd Rausch <gerd.rausch@oracle.com>
Cc: santosh.shilimkar@oracle.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [PATCH net 1/1] net/rds: dma_map_sg is entitled to merge entries
Date: Wed, 18 Aug 2021 22:40:06 +0000 [thread overview]
Message-ID: <162932640671.7744.17327639180995052321.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <60efc69f-1f35-529d-a7ef-da0549cad143@oracle.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 17 Aug 2021 10:04:37 -0700 you wrote:
> Function "dma_map_sg" is entitled to merge adjacent entries
> and return a value smaller than what was passed as "nents".
>
> Subsequently "ib_map_mr_sg" needs to work with this value ("sg_dma_len")
> rather than the original "nents" parameter ("sg_len").
>
> This old RDS bug was exposed and reliably causes kernel panics
> (using RDMA operations "rds-stress -D") on x86_64 starting with:
> commit c588072bba6b ("iommu/vt-d: Convert intel iommu driver to the iommu ops")
>
> [...]
Here is the summary with links:
- [net,1/1] net/rds: dma_map_sg is entitled to merge entries
https://git.kernel.org/netdev/net/c/fb4b1373dcab
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:[~2021-08-18 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 17:04 [PATCH net 1/1] net/rds: dma_map_sg is entitled to merge entries Gerd Rausch
2021-08-17 17:07 ` Santosh Shilimkar
2021-08-18 22:40 ` 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=162932640671.7744.17327639180995052321.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gerd.rausch@oracle.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.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).