From: patchwork-bot+linux-riscv@kernel.org
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-riscv@lists.infradead.org, alex@ghiti.fr,
aou@eecs.berkeley.edu, iommu@lists.linux.dev, joro@8bytes.org,
palmer@dabbelt.com, pjw@kernel.org, robin.murphy@arm.com,
will@kernel.org, baolu.lu@linux.intel.com, jroedel@suse.de,
palmer@rivosinc.com, patches@lists.linux.dev,
tjeznach@rivosinc.com, zong.li@sifive.com
Subject: Re: [PATCH] iommu/riscv: Remove overflows on the invalidation path
Date: Thu, 30 Apr 2026 03:25:04 +0000 [thread overview]
Message-ID: <177751950479.2274119.1171635926750026675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0-v1-0f76ffba5af6+11540-iommupt_inv_riscv_jgg@nvidia.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Joerg Roedel <joerg.roedel@amd.com>:
On Fri, 27 Mar 2026 12:22:10 -0300 you wrote:
> Since RISC-V supports a sign extended page table it should support
> a gather->end of ULONG_MAX, but if this happens it will infinite loop
> because of the overflow.
>
> Also avoid overflow computing the length by moving the +1 to the other
> side of the <
>
> [...]
Here is the summary with links:
- iommu/riscv: Remove overflows on the invalidation path
https://git.kernel.org/riscv/c/40a13b499579
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-04-30 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:22 [PATCH] iommu/riscv: Remove overflows on the invalidation path Jason Gunthorpe
2026-04-02 7:36 ` Joerg Roedel
2026-04-30 3:25 ` patchwork-bot+linux-riscv [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=177751950479.2274119.1171635926750026675.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=patches@lists.linux.dev \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=will@kernel.org \
--cc=zong.li@sifive.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