From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org, Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH] blspec: skip entries that are not blspec entries
Date: Mon, 23 Sep 2019 20:30:35 +0200 [thread overview]
Message-ID: <4e5e80d0-2ef2-c474-027f-2b8d0a2bf17a@pengutronix.de> (raw)
In-Reply-To: <20190920124433.31026-1-m.tretter@pengutronix.de>
On 9/20/19 2:44 PM, Michael Tretter wrote:
> The list of boot entries can contain items that are not blspec entries.
> For example, the bootchooser also adds an item to this list. Therefore,
> blspec cannot unconditionally interpret entries as blspec entries.
>
> The error is reproduced by listing the boot entries with the bootchooser
> and a rootfs with blspec entries, e.g.:
>
> boot -l bootchooser /mnt/nfs
>
> Check if a bootentry is a blspec entry by testing if the boot function
> is blspec_boot.
>
> Reported-by: Thomas Hämmerle <Thomas.Haemmerle@wolfvision.net>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
> common/blspec.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/common/blspec.c b/common/blspec.c
> index 66e5033e35..3b148e2ab4 100644
> --- a/common/blspec.c
> +++ b/common/blspec.c
> @@ -228,6 +228,14 @@ static struct blspec_entry *blspec_entry_open(struct bootentries *bootentries,
> return entry;
> }
>
> +/*
> + * is_blspec_entry - check if a bootentry is a blspec entry
> + */
> +static inline bool is_blspec_entry(struct bootentry *entry)
> +{
> + return entry.boot == blspec_boot;
entry is a pointer. This doesn't compile:
./common/blspec.c:314:14: error: 'entry' is a pointer; did you mean to use '->'?
314 | return entry.boot == blspec_boot;
> +}
> +
> /*
> * blspec_have_entry - check if we already have an entry with
> * a certain path
> @@ -238,6 +246,8 @@ static int blspec_have_entry(struct bootentries *bootentries, const char *path)
> struct blspec_entry *e;
>
> list_for_each_entry(be, &bootentries->entries, list) {
> + if (!is_blspec_entry(be))
> + continue;
> e = container_of(be, struct blspec_entry, entry);
> if (e->configpath && !strcmp(e->configpath, path))
> return 1;
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-09-23 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 12:44 Michael Tretter
2019-09-23 6:50 ` Sascha Hauer
2019-09-23 18:30 ` Ahmad Fatoum [this message]
2019-09-24 7:55 ` Michael Tretter
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=4e5e80d0-2ef2-c474-027f-2b8d0a2bf17a@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@pengutronix.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