linux-kernel - Re: Re: [v4] iommu/riscv: prevent NULL deref in iova_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250820111643.19464-1-huangxianliang@lanxincomputing.com>
Date: Wed, 20 Aug 2025 19:16:43 +0800
From: "XianLiang Huang" <huangxianliang@...xincomputing.com>
To: <markus.elfring@....de>
Cc: <alex@...ti.fr>, <aou@...s.berkeley.edu>, 
	<huangxianliang@...xincomputing.com>, <iommu@...ts.linux.dev>, 
	<joro@...tes.org>, <linux-kernel@...r.kernel.org>, 
	<linux-riscv@...ts.infradead.org>, <palmer@...belt.com>, 
	<paul.walmsley@...ive.com>, <robin.murphy@....com>, 
	<tjeznach@...osinc.com>, <will@...nel.org>
Subject: Re: Re: [v4] iommu/riscv: prevent NULL deref in iova_to_phys

> Does it trigger undesirable communication difficulties?
No, and I agree that both subject and summary phrase can be improved

And now I do learn from this, thanks.
> Your patch will almost certainly get comments from reviewers on ways in
> which the patch can be improved, in the form of a reply to your email. You must
> respond to those comments; ignoring reviewers is a good way to get ignored in
> return. You can simply reply to their emails to answer their comments. Review
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n310

Regards,
Xianliang