From: David Gibson <david@gibson.dropbear.id.au>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH] checks: Check the overall length of "interrupt-map"
Date: Sat, 1 Jun 2024 18:31:05 +1000 [thread overview]
Message-ID: <ZlrcSdOSx2MX1_6g@zatzit> (raw)
In-Reply-To: <20240531133149.1498139-1-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On Fri, May 31, 2024 at 08:31:49AM -0500, Rob Herring (Arm) wrote:
> It is possible the overall length of "interrupt-map" is shorter than
> expected. A likely scenario is if "#address-cells" in the interrupt
> parent is not accounted for and there is only a single map entry. With
> multiple entries, one of the other tests would likely fail.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Applied, thanks. Of course, a test case for this would be a nice followup.
> ---
> checks.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/checks.c b/checks.c
> index 28f86ccff56b..1950c18dd333 100644
> --- a/checks.c
> +++ b/checks.c
> @@ -1677,6 +1677,10 @@ static void check_interrupt_map(struct check *c,
> parent_cellsize += propval_cell(cellprop);
>
> cell += 1 + parent_cellsize;
> + if (cell > map_cells)
> + FAIL_PROP(c, dti, node, irq_map_prop,
> + "property size (%d) mismatch, expected %zu",
> + irq_map_prop->val.len, cell * sizeof(cell_t));
> }
> }
> WARNING(interrupt_map, check_interrupt_map, NULL, &phandle_references, &addr_size_cells, &interrupt_provider);
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-01 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 13:31 [PATCH] checks: Check the overall length of "interrupt-map" Rob Herring (Arm)
2024-06-01 8:31 ` David Gibson [this message]
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=ZlrcSdOSx2MX1_6g@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=robh@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.