From: Robert Baldyga <r.baldyga@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: avoid dev->req_seq overflow
Date: Fri, 19 Sep 2014 07:25:36 +0200 [thread overview]
Message-ID: <541BBE50.9060107@samsung.com> (raw)
In-Reply-To: <CAPnjgZ2NaCANp4e64XeAzRx+t0y4-ktQyQcUFsqhMsWjjLrX3g@mail.gmail.com>
On 09/18/2014 08:00 PM, Simon Glass wrote:
> Hi Robert,
>
> On 18 September 2014 09:13, Robert Baldyga <r.baldyga@samsung.com
> <mailto:r.baldyga@samsung.com>> wrote:
>
> Since dev->req_seq value is initialized from "reg" property of fdt node,
> there is posibility, that address value contained in fdt is greater than
> INT_MAX, and then value in dev->req_seq is negative which led to probe()
> fail.
>
> This patch fix this problem by ensuring that req_seq is positive, unless
> it's one of errno codes.
>
>
> Wouldn't this be a bug in the device tree file? What does it mean to
> have a -ve value?
>
Device tree seems to be ok. We have:
pinctrl0: pinctrl at e0200000 {
compatible = "samsung,s5pc110-pinctrl";
reg = <0xe0200000 0x1000>;
};
So when we take address from "reg" as dev->req_seq, then value
0xe0200000 after casting to int gives -534773760. Function
uclass_resolve_seq() returns it as proper seq number, because it's
unique. But then in file drivers/core/device.c, in function
device_probe() we have:
seq = uclass_resolve_seq(dev);
if (seq < 0) {
ret = seq;
goto fail;
}
And it will obviously fail.
Using "reg" value as req_seq doesn't work when this value is greater
than INT_MAX.
>
> Signed-off-by: Robert Baldyga <r.baldyga@samsung.com
> <mailto:r.baldyga@samsung.com>>
> ---
> drivers/core/device.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/core/device.c b/drivers/core/device.c
> index 166b073..35ffce0 100644
> --- a/drivers/core/device.c
> +++ b/drivers/core/device.c
> @@ -107,6 +107,8 @@ int device_bind(struct udevice *parent, struct
> driver *drv, const char *name,
> * when the device is probed.
> */
> dev->req_seq = fdtdec_get_int(gd->fdt_blob, of_offset,
> "reg", -1);
> + if (!IS_ERR_VALUE(dev->req_seq))
> + dev->req_seq &= INT_MAX;
> dev->seq = -1;
> if (uc->uc_drv->name && of_offset != -1) {
> fdtdec_get_alias_seq(gd->fdt_blob, uc->uc_drv->name,
> of_offset,
> --
> 1.9.1
>
Thanks,
Robert Baldyga
next prev parent reply other threads:[~2014-09-19 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:13 [U-Boot] [PATCH] dm: avoid dev->req_seq overflow Robert Baldyga
2014-09-18 18:00 ` Simon Glass
2014-09-19 5:25 ` Robert Baldyga [this message]
2014-09-19 17:49 ` Simon Glass
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=541BBE50.9060107@samsung.com \
--to=r.baldyga@samsung.com \
--cc=u-boot@lists.denx.de \
/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.