[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54773557.6020600@suse.de>
Date: Thu, 27 Nov 2014 15:29:43 +0100
From: Alexander Graf <agraf@...e.de>
To: "J. German Rivera" <German.Rivera@...escale.com>,
gregkh@...uxfoundation.org, arnd@...db.de,
linux-kernel@...r.kernel.org
CC: stuart.yoder@...escale.com, Kim.Phillips@...escale.com,
scottwood@...escale.com, bhamciu1@...escale.com,
R89243@...escale.com, Geoff.Thorpe@...escale.com,
bhupesh.sharma@...escale.com, nir.erez@...escale.com,
richard.schmitt@...escale.com
Subject: Re: [PATCH 1/3 v4] drivers/bus: Added Freescale Management Complex
APIs
On 13.11.14 18:54, J. German Rivera wrote:
> APIs to access the Management Complex (MC) hardware
> module of Freescale LS2 SoCs. This patch includes
> APIs to check the MC firmware version and to manipulate
> DPRC objects in the MC.
>
> Signed-off-by: J. German Rivera <German.Rivera@...escale.com>
> Signed-off-by: Stuart Yoder <stuart.yoder@...escale.com>
[...]
> +/*
> + * Object descriptor, returned from dprc_get_obj()
> + */
> +struct dprc_obj_desc {
> + /* Type of object: NULL terminated string */
> + char type[16];
I don't see where it actually gets NULL terminated - all 16 bytes come
directly from the device.
While it's probably ok to trust it, I think we'd still be safer off if
we just make this a char[17] array to always have our NULL terminating
string. That way we're guaranteed we'll never run over our memory
boundaries.
Also sorry for the slowly trickling in comments - I'm just noting things
as I dig through the whole interface :).
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists