From: Jason Gunthorpe <jgg@nvidia.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: linux-rdma@vger.kernel.org, leonro@nvidia.com,
Selvin Xavier <selvin.xavier@broadcom.com>,
Andrew Gospodarek <andrew.gospodarek@broadcom.com>
Subject: Re: [PATCH rdma-rc v1] RDMA/core: fix sg_to_page mapping for boundary condition
Date: Tue, 20 Sep 2022 16:14:35 -0300 [thread overview]
Message-ID: <YyoRGzNiPLwVZYjf@nvidia.com> (raw)
In-Reply-To: <fc18b231b93a47b8ca1314f3778bfe1a@mail.gmail.com>
On Mon, Sep 12, 2022 at 04:32:09PM +0530, Kashyap Desai wrote:
> I noted your response. Issue is possible to any RDMA h/w and issue is not
> completely Rejected. It is just that you need another way to fix it
> (preferred to handle it in iommu)
> We can reopen discussion if we see another instance from other vendors.
> Quick workaround is - use 63 bit DMA mask in rdma low level driver if
> someone really wants to work around this issue until something more robust
> fix committed in upstream kernel (either ib stack or iommu stack).
That is not quite right, I said it should also be fixed in RDMA, just
none of the patches you are proposing fix it correctly. You must avoid
the mathematical overflow by reworking the logic.
Jason
prev parent reply other threads:[~2022-09-20 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:11 [PATCH rdma-rc v1] RDMA/core: fix sg_to_page mapping for boundary condition Kashyap Desai
2022-08-18 23:52 ` Jason Gunthorpe
2022-08-19 9:43 ` Kashyap Desai
2022-08-19 11:48 ` Jason Gunthorpe
2022-08-22 14:21 ` Kashyap Desai
2022-08-26 13:14 ` Jason Gunthorpe
2022-09-01 12:06 ` Kashyap Desai
2022-09-06 17:33 ` Jason Gunthorpe
2022-09-12 11:02 ` Kashyap Desai
2022-09-20 19:14 ` Jason Gunthorpe [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=YyoRGzNiPLwVZYjf@nvidia.com \
--to=jgg@nvidia.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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 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.