All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: XianLiang Huang <huangxianliang@lanxincomputing.com>
Cc: linux-riscv@lists.infradead.org, tjeznach@rivosinc.com,
	markus.elfring@web.de, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] iommu/riscv: prevent NULL deref in iova_to_phys
Date: Thu, 09 Oct 2025 01:07:01 +0000	[thread overview]
Message-ID: <175997202124.3661959.1599667136766880381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820072248.312-1-huangxianliang@lanxincomputing.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Joerg Roedel <joerg.roedel@amd.com>:

On Wed, 20 Aug 2025 15:22:48 +0800 you wrote:
> The riscv_iommu_pte_fetch() function returns either NULL for
> unmapped/never-mapped iova, or a valid leaf pte pointer that requires no
> further validation.
> 
> riscv_iommu_iova_to_phys() failed to handle NULL returns. Prevent null pointer
> dereference in riscv_iommu_iova_to_phys(), and remove the pte validation.
> 
> [...]

Here is the summary with links:
  - [v4] iommu/riscv: prevent NULL deref in iova_to_phys
    https://git.kernel.org/riscv/c/99d4d1a07087

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: XianLiang Huang <huangxianliang@lanxincomputing.com>
Cc: linux-riscv@lists.infradead.org, tjeznach@rivosinc.com,
	markus.elfring@web.de, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] iommu/riscv: prevent NULL deref in iova_to_phys
Date: Thu, 09 Oct 2025 01:07:01 +0000	[thread overview]
Message-ID: <175997202124.3661959.1599667136766880381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820072248.312-1-huangxianliang@lanxincomputing.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Joerg Roedel <joerg.roedel@amd.com>:

On Wed, 20 Aug 2025 15:22:48 +0800 you wrote:
> The riscv_iommu_pte_fetch() function returns either NULL for
> unmapped/never-mapped iova, or a valid leaf pte pointer that requires no
> further validation.
> 
> riscv_iommu_iova_to_phys() failed to handle NULL returns. Prevent null pointer
> dereference in riscv_iommu_iova_to_phys(), and remove the pte validation.
> 
> [...]

Here is the summary with links:
  - [v4] iommu/riscv: prevent NULL deref in iova_to_phys
    https://git.kernel.org/riscv/c/99d4d1a07087

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

  parent reply	other threads:[~2025-10-09  1:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20  7:22 [PATCH v4] iommu/riscv: prevent NULL deref in iova_to_phys XianLiang Huang
2025-08-20  7:22 ` XianLiang Huang
2025-08-20  8:25 ` Markus Elfring
2025-08-20  8:25   ` Markus Elfring
2025-08-20  9:21   ` XianLiang Huang
2025-08-20  9:21     ` XianLiang Huang
2025-08-20 10:40     ` [v4] " Markus Elfring
2025-08-20 10:40       ` Markus Elfring
2025-08-20 11:16       ` XianLiang Huang
2025-08-20 11:16         ` XianLiang Huang
2025-08-20 11:30         ` Markus Elfring
2025-08-20 11:30           ` Markus Elfring
2025-08-22  2:36           ` XianLiang Huang
2025-08-22  2:36             ` XianLiang Huang
2025-08-22  6:52 ` [PATCH v4] " Joerg Roedel
2025-08-22  6:52   ` Joerg Roedel
2025-10-09  1:07 ` patchwork-bot+linux-riscv [this message]
2025-10-09  1:07   ` patchwork-bot+linux-riscv

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=175997202124.3661959.1599667136766880381.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=huangxianliang@lanxincomputing.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=markus.elfring@web.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robin.murphy@arm.com \
    --cc=tjeznach@rivosinc.com \
    --cc=will@kernel.org \
    /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.