From: Markus Elfring <Markus.Elfring@web.de>
To: Huang XianLiang <huangxianliang@lanxincomputing.com>,
iommu@lists.linux.dev, linux-riscv@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>, "Jörg Rödel" <joro@8bytes.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Tomasz Jeznach" <tjeznach@rivosinc.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH] iommu/riscv: check pte null pointer before use
Date: Tue, 5 Aug 2025 13:17:26 +0200 [thread overview]
Message-ID: <1f419739-4233-474d-b00a-4e1237352691@web.de> (raw)
In-Reply-To: <20250805101741.30819-1-huangxianliang@lanxincomputing.com>
…
> This commit just check the pointer before using it to avoid the bug.
…
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n94
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n145
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Huang XianLiang <huangxianliang@lanxincomputing.com>,
iommu@lists.linux.dev, linux-riscv@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>, "Jörg Rödel" <joro@8bytes.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Tomasz Jeznach" <tjeznach@rivosinc.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH] iommu/riscv: check pte null pointer before use
Date: Tue, 5 Aug 2025 13:17:26 +0200 [thread overview]
Message-ID: <1f419739-4233-474d-b00a-4e1237352691@web.de> (raw)
In-Reply-To: <20250805101741.30819-1-huangxianliang@lanxincomputing.com>
…
> This commit just check the pointer before using it to avoid the bug.
…
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n94
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n145
Regards,
Markus
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-08-05 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 10:17 [PATCH] iommu/riscv: check pte null pointer before use Huang XianLiang
2025-08-05 10:17 ` Huang XianLiang
2025-08-05 11:17 ` Markus Elfring [this message]
2025-08-05 11:17 ` Markus Elfring
2025-08-06 10:13 ` XianLiang Huang
2025-08-06 10:13 ` XianLiang Huang
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=1f419739-4233-474d-b00a-4e1237352691@web.de \
--to=markus.elfring@web.de \
--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=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.