From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Albert Esteve <aesteve@redhat.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sarannya S <quic_sarannya@oss.qualcomm.com>,
Pranav Mahesh Phansalkar <quic_pphansal@oss.qualcomm.com>,
Sudeepgoud Patil <quic_sudeepgo@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/2] soc: qcom: smem: add boundary checks for partitions
Date: Wed, 23 Sep 2026 15:58:42 +0200 [thread overview]
Message-ID: <b3ae48e9-c2fc-4d04-8926-503fa6192c1d@oss.qualcomm.com> (raw)
In-Reply-To: <20260904-port-smem-v2-1-bb497dd3c48b@redhat.com>
On 9/4/26 5:18 PM, Albert Esteve wrote:
> From: Sarannya S <quic_sarannya@oss.qualcomm.com>
>
> Add condition check to make sure that the end address
> of private entry does not go out of partition.
[...]
> @@ -409,6 +421,7 @@ static int qcom_smem_alloc_private(struct qcom_smem *smem,
> size_t size)
> {
> struct smem_private_entry *hdr, *end;
> + struct smem_private_entry *next_hdr;
> struct smem_partition_header *phdr;
> size_t alloc_size;
> void *cached;
> @@ -421,19 +434,25 @@ static int qcom_smem_alloc_private(struct qcom_smem *smem,
> end = phdr_to_last_uncached_entry(phdr);
> cached = phdr_to_last_cached_entry(phdr);
>
> - if (WARN_ON((void *)end > p_end || cached > p_end))
> + if (WARN_ON(!IN_PARTITION_RANGE(end, 0, phdr, cached) ||
> + cached > p_end))
strange indentation
> return -EINVAL;
>
> - while (hdr < end) {
> + while ((hdr < end) && ((hdr + 1) < end)) {
I believe the latter implies the former
[...]
> e = phdr_to_first_uncached_entry(phdr);
> - end = phdr_to_last_uncached_entry(phdr);
> + uncached_end = phdr_to_last_uncached_entry(phdr);
> + cached_end = phdr_to_last_cached_entry(phdr);
> +
> + if (WARN_ON(!IN_PARTITION_RANGE(uncached_end, 0, phdr, cached_end)
> + || (void *)cached_end > p_end))
The || usually goes on the end of the line, please move it there
This patch changes a lot without much explanation, could you please
split it up so that the changes are more focused? I know the general
theme is overflow checks, but a lot of conditions change
simultaneously in its current form and it's hard to track, even GPT
is slightly confused
Konrad
next prev parent reply other threads:[~2026-09-23 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 15:18 [PATCH v2 0/2] Add automotive SMEM hardening for Qualcomm platforms Albert Esteve
2026-09-04 15:18 ` [PATCH v2 1/2] soc: qcom: smem: add boundary checks for partitions Albert Esteve
2026-09-23 13:58 ` Konrad Dybcio [this message]
2026-09-23 14:49 ` Albert Esteve
2026-09-04 15:18 ` [PATCH v2 2/2] soc: qcom: smem: ignore multi remote host partitions Albert Esteve
2026-09-23 13:38 ` Konrad Dybcio
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=b3ae48e9-c2fc-4d04-8926-503fa6192c1d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=aesteve@redhat.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_pphansal@oss.qualcomm.com \
--cc=quic_sarannya@oss.qualcomm.com \
--cc=quic_sudeepgo@oss.qualcomm.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
all inboxes | Powered by JetHome®