U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jaehoon Chung" <jh80.chung@samsung.com>
To: "'Marek Vasut'" <marek.vasut@mailbox.org>, <u-boot@lists.denx.de>
Cc: <trini@konsulko.com>, <sjg@chromium.org>,
	<marek.vasut+renesas@mailbox.org>,
	<laurent.pinchart@ideasonboard.com>, <m.szyprowski@samsung.com>
Subject: RE: [PATCH] boot: image-board: Mismatch a type between variable and return value
Date: Wed, 6 Nov 2024 08:47:09 +0900	[thread overview]
Message-ID: <02ea01db2fdd$0799f610$16cde230$@samsung.com> (raw)
In-Reply-To: <a3ad60cd-c8f4-4377-a30f-80f1530313eb@mailbox.org>


> -----Original Message-----
> From: Marek Vasut <marek.vasut@mailbox.org>
> Sent: Wednesday, November 6, 2024 7:57 AM
> To: Jaehoon Chung <jh80.chung@samsung.com>; u-boot@lists.denx.de
> Cc: trini@konsulko.com; sjg@chromium.org; marek.vasut+renesas@mailbox.org;
> laurent.pinchart@ideasonboard.com; m.szyprowski@samsung.com
> Subject: Re: [PATCH] boot: image-board: Mismatch a type between variable and return value
>
> On 11/5/24 11:11 PM, Jaehoon Chung wrote:
> > phys_addr_t can be used unsigned long long type with CONFIG_PHYS_64BIT.
> > But hextoul() is always returning to unsigned long. It can be assigned
> > to unexpected value. To avoid wrong behavior, change from hextoul() to
> > simple_strtoull().
> >
> > Fixes: a4df06e41fa2 ("boot: fdt: Change type of env_get_bootm_low() to phys_addr_t")
>
> Looking at:
>
> 7e5f460ec457 ("global: Convert simple_strtoul() with hex to hextoul()")

Thanks for informing it.

>
> do you have to update any of the other hextoul() calls too ?

I didn't check other hextoul().
During booting with initramfs on RPi (32bit), I found the problem that is not working fine because of this.

>
> Maybe we need hextoull() ?

IMO, We need hextoull() for some cases.
If there is no objection, I will send the patch for adding hextoull().
And I will check entire cases.

Best Regards,
Jaehoon Chung

>
> > Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> > ---
> >   boot/image-board.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/boot/image-board.c b/boot/image-board.c
> > index 1757e5816d84..977343a8995c 100644
> > --- a/boot/image-board.c
> > +++ b/boot/image-board.c
> > @@ -547,7 +547,7 @@ int boot_ramdisk_high(ulong rd_data, ulong rd_len, ulong *initrd_start,
> >   		/* a value of "no" or a similar string will act like 0,
> >   		 * turning the "load high" feature off. This is intentional.
> >   		 */
> > -		initrd_high = hextoul(s, NULL);
> > +		initrd_high = simple_strtoull(s, NULL, 16);
> >   		if (initrd_high == ~0)
> >   			initrd_copy_to_ram = 0;
> >   	} else {
>




  reply	other threads:[~2024-11-05 23:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20241105221151epcas1p2096fdad52d8b4977f707e4b1b3a47849@epcas1p2.samsung.com>
2024-11-05 22:11 ` [PATCH] boot: image-board: Mismatch a type between variable and return value Jaehoon Chung
2024-11-05 22:57   ` Marek Vasut
2024-11-05 23:47     ` Jaehoon Chung [this message]
2024-11-06  2:12       ` Marek Vasut

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='02ea01db2fdd$0799f610$16cde230$@samsung.com' \
    --to=jh80.chung@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=m.szyprowski@samsung.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=marek.vasut@mailbox.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox