mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [RFC] uimagefs segmentation fault
Date: Thu, 4 Jan 2024 01:04:04 +0300	[thread overview]
Message-ID: <20240104010404.c88b208689aca142c3828bf8@gmail.com> (raw)

Hi!

I have prepared a linux uImage file for testing my uImage-related patches.

barebox$ dumpimage -l ./defaultenv/defaultenv-2-base/uImage
Image Name:   Linux-6.7.0-rc4-00003-ge185a416f
Created:      Wed Jan  3 15:28:27 2024
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    6131616 Bytes = 5987.91 KiB = 5.85 MiB
Load Address: 00000000
Entry Point:  00000000

I tryed to mount my uImage under mainline master sandbox barebox:

barebox@Sandbox:/ mount -t uimagefs env/uImage /mnt/
Segmentation fault

The problem is in the uimagefs_add_str(). if s == NULL then strlen() fails:

static int uimagefs_add_str(struct uimagefs_handle *priv, enum uimagefs_type type,
                                char *s)
{
        struct uimagefs_handle_data *d;

        d = xzalloc(sizeof(*d));
        d->type = type;
        d->name = xstrdup(uimagefs_type_to_str(type));
        d->data = s;
        d->size = strlen(s); <<<<<<<<<<<<<<<<<<<<<<<<<<< s == NULL!

        list_add_tail(&d->list, &priv->list);

        return 0;
}


It looks like my uImage lacks some attributes, e.g. "os".

So I can propose several solutions for the problem:

1. don't call strlen(s) if s == NULL:

@@ -226,7 +226,7 @@ static int uimagefs_add_str(struct uimagefs_handle *priv, enum uimagefs_type typ
        d->type = type;
        d->name = xstrdup(uimagefs_type_to_str(type));
        d->data = s;
-       d->size = strlen(s);
+       d->size = (s != NULL) ? strlen(s) : 0;

        list_add_tail(&d->list, &priv->list);

So we will have empty files (len == 0) for absent attributes.

2. regard the s == NULL situation as error:

@@ -222,6 +222,9 @@ static int uimagefs_add_str(struct uimagefs_handle *priv, enum uimagefs_type typ
 {
        struct uimagefs_handle_data *d;
 
+       if (!s)
+               return -ENODATA;
+
        d = xzalloc(sizeof(*d));
        d->type = type;
        d->name = xstrdup(uimagefs_type_to_str(type));

So we can't mount uImages without required attributes.

3. don't show absent attributes, e.g.:

@@ -222,6 +222,9 @@ static int uimagefs_add_str(struct uimagefs_handle *priv, enum uimagefs_type typ
 {
        struct uimagefs_handle_data *d;
 
+       if (!s)
+               return -ENODATA;
+
        d = xzalloc(sizeof(*d));
        d->type = type;
        d->name = xstrdup(uimagefs_type_to_str(type));
@@ -421,7 +421,7 @@ static int __uimage_open(struct uimagefs_handle *priv)
                goto err_out;
 
        ret = uimagefs_add_os(priv);
-       if (ret)
+       if (ret && ret != -ENODATA)
                goto err_out;
 
        ret = uimagefs_add_time(priv);


I'm not a skilled uImage user so I have no idea which solution is acceptable for the users.

Please comment!

-- 
Best regards,
  Antony Pavlov



             reply	other threads:[~2024-01-03 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 22:04 Antony Pavlov [this message]
2024-01-04 11:35 ` Sascha Hauer

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=20240104010404.c88b208689aca142c3828bf8@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox