From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Zheng Zengkai <zhengzengkai@huawei.com>,
will@kernel.org, catalin.marinas@arm.com
Cc: guohanjun@huawei.com, sudeep.holla@arm.com, mark.rutland@arm.com,
maz@kernel.org, rafael@kernel.org, lenb@kernel.org,
daniel.lezcano@linaro.org, tglx@linutronix.de,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ACPI: GTDT: Tighten the check for the array of platform timer structures
Date: Wed, 30 Oct 2024 10:49:13 +0100 [thread overview]
Message-ID: <ZyIBGRv/10kpOcOl@lpieralisi> (raw)
In-Reply-To: <3bf1fe29-e135-c1ba-2774-d1e98c8b92b3@huawei.com>
[+Catalin/Will]
On Tue, Oct 29, 2024 at 10:16:41PM +0800, Zheng Zengkai wrote:
>
> Gentle ping.
>
> This patch still can be applied to upstream now.
Hi Catalin, Will,
this patch is a clean-up - not a fix, it could be merged
for v6.13, please consider it if there is still time.
Thanks,
Lorenzo
>
> Thanks!
>
>
> 在 2024/10/16 18:01, Lorenzo Pieralisi 写道:
> > On Wed, Oct 16, 2024 at 05:54:58PM +0800, Zheng Zengkai wrote:
> > > As suggested by Marc and Lorenzo, first we need to check whether the
> > > platform_timer entry pointer is within gtdt bounds (< gtdt_end) before
> > > de-referencing what it points at to detect the length of the platform
> > > timer struct and then check that the length of current platform_timer
> > > struct is also valid, i.e. the length is not zero and within gtdt_end.
> > > Now next_platform_timer() only checks against gtdt_end for the entry of
> > > subsequent platform timer without checking the length of it and will
> > > not report error if the check failed and the existing check in function
> > > acpi_gtdt_init() is also not enough.
> > >
> > > Modify the for_each_platform_timer() iterator and use it combined with
> > > a dedicated check function platform_timer_valid() to do the check
> > > against table length (gtdt_end) for each element of platform timer
> > > array in function acpi_gtdt_init(), making sure that both their entry
> > > and length actually fit in the table.
> > >
> > > Suggested-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> > > Co-developed-by: Marc Zyngier <maz@kernel.org>
> > > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > > Signed-off-by: Zheng Zengkai <zhengzengkai@huawei.com>
> > > ---
> > > Changes in v4:
> > > - remove the tmp pointer to make the code more concise.
> > >
> > > Changes in v3:
> > > - based on Marc's patch and reuse the for_each_platform_timer() loop
> > > Link to v3: https://lore.kernel.org/linux-arm-kernel/20241015152602.184108-1-zhengzengkai@huawei.com/
> > >
> > > Changes in v2:
> > > - Check against gtdt_end for both entry and len of each array element
> > > Link to v2: https://lore.kernel.org/linux-arm-kernel/20241012085343.6594-1-zhengzengkai@huawei.com/
> > >
> > > Link to v1: https://lore.kernel.org/all/20241010144703.113728-1-zhengzengkai@huawei.com/
> > >
> > > Link to previous related patches:
> > > https://lore.kernel.org/all/20241008082429.33646-1-zhengzengkai@huawei.com/
> > > https://lore.kernel.org/all/20240930030716.179992-1-zhengzengkai@huawei.com/
> > > ---
> > > drivers/acpi/arm64/gtdt.c | 29 ++++++++++++++++++++---------
> > > 1 file changed, 20 insertions(+), 9 deletions(-)
> > Reviewed-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> >
> > > diff --git a/drivers/acpi/arm64/gtdt.c b/drivers/acpi/arm64/gtdt.c
> > > index c0e77c1c8e09..d7c4e1b9915b 100644
> > > --- a/drivers/acpi/arm64/gtdt.c
> > > +++ b/drivers/acpi/arm64/gtdt.c
> > > @@ -36,19 +36,25 @@ struct acpi_gtdt_descriptor {
> > > static struct acpi_gtdt_descriptor acpi_gtdt_desc __initdata;
> > > -static inline __init void *next_platform_timer(void *platform_timer)
> > > +static __init bool platform_timer_valid(void *platform_timer)
> > > {
> > > struct acpi_gtdt_header *gh = platform_timer;
> > > - platform_timer += gh->length;
> > > - if (platform_timer < acpi_gtdt_desc.gtdt_end)
> > > - return platform_timer;
> > > + return (platform_timer >= (void *)(acpi_gtdt_desc.gtdt + 1) &&
> > > + platform_timer < acpi_gtdt_desc.gtdt_end &&
> > > + gh->length != 0 &&
> > > + platform_timer + gh->length <= acpi_gtdt_desc.gtdt_end);
> > > +}
> > > +
> > > +static __init void *next_platform_timer(void *platform_timer)
> > > +{
> > > + struct acpi_gtdt_header *gh = platform_timer;
> > > - return NULL;
> > > + return platform_timer + gh->length;
> > > }
> > > #define for_each_platform_timer(_g) \
> > > - for (_g = acpi_gtdt_desc.platform_timer; _g; \
> > > + for (_g = acpi_gtdt_desc.platform_timer; platform_timer_valid(_g);\
> > > _g = next_platform_timer(_g))
> > > static inline bool is_timer_block(void *platform_timer)
> > > @@ -157,6 +163,7 @@ int __init acpi_gtdt_init(struct acpi_table_header *table,
> > > {
> > > void *platform_timer;
> > > struct acpi_table_gtdt *gtdt;
> > > + int cnt = 0;
> > > gtdt = container_of(table, struct acpi_table_gtdt, header);
> > > acpi_gtdt_desc.gtdt = gtdt;
> > > @@ -176,12 +183,16 @@ int __init acpi_gtdt_init(struct acpi_table_header *table,
> > > return 0;
> > > }
> > > - platform_timer = (void *)gtdt + gtdt->platform_timer_offset;
> > > - if (platform_timer < (void *)table + sizeof(struct acpi_table_gtdt)) {
> > > + acpi_gtdt_desc.platform_timer = (void *)gtdt + gtdt->platform_timer_offset;
> > > + for_each_platform_timer(platform_timer)
> > > + cnt++;
> > > +
> > > + if (cnt != gtdt->platform_timer_count) {
> > > + acpi_gtdt_desc.platform_timer = NULL;
> > > pr_err(FW_BUG "invalid timer data.\n");
> > > return -EINVAL;
> > > }
> > > - acpi_gtdt_desc.platform_timer = platform_timer;
> > > +
> > > if (platform_timer_count)
> > > *platform_timer_count = gtdt->platform_timer_count;
> > > --
> > > 2.20.1
> > >
> > .
> >
next prev parent reply other threads:[~2024-10-30 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 9:54 [PATCH v4] ACPI: GTDT: Tighten the check for the array of platform timer structures Zheng Zengkai
2024-10-16 10:01 ` Lorenzo Pieralisi
2024-10-29 14:16 ` Zheng Zengkai
2024-10-30 9:49 ` Lorenzo Pieralisi [this message]
2024-10-19 6:41 ` Hanjun Guo
2024-10-19 7:35 ` Hanjun Guo
2024-11-04 17:10 ` Catalin Marinas
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=ZyIBGRv/10kpOcOl@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=zhengzengkai@huawei.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