From: "Pali Rohár" <pali@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: Derek LaHousse <derek@seaofdirac.org>,
u-boot@lists.denx.de, sr@denx.de, kostap@marvell.com
Subject: Re: [PATCH 1/1] mvebu: fix end-of-array check
Date: Sun, 4 Dec 2022 22:51:03 +0100 [thread overview]
Message-ID: <20221204215103.bbmc3gko2haebs4m@pali> (raw)
In-Reply-To: <CAPnjgZ26FGEgi2E5iCd8d1NubKgknOLdg_ek7PYVdnp2=2Y-kQ@mail.gmail.com>
On Monday 05 December 2022 10:16:51 Simon Glass wrote:
> On Thu, 1 Dec 2022 at 07:55, Derek LaHousse <derek@seaofdirac.org> wrote:
> >
> > Properly seek the end of default_environment variables.
> >
> > The current algorithm overwrites from the second variable. This
> > replacement finds the end of the array of strings.
> >
> > Stomped variables include "board", "soc", "loadaddr". These can be
> > seen on a "env default -a" after patch, but they are not seen with a
> > version before the patch.
> >
> > Signed-off-by: Derek LaHousse <derek@seaofdirac.org>
> > ---
> > board/Marvell/mvebu_armada-37xx/board.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> It seems odd to update the default environment, but if we want to do
> this, it should really be done in a function in env/ along with some
> tests in test/env
>
> Regards,
> Simon
Well, this is just a temporary solution until Marek's env patch series is merged:
https://lore.kernel.org/u-boot/20211103232332.2737-1-kabel@kernel.org/
But I agree that tests would prevent these bugs.
next prev parent reply other threads:[~2022-12-04 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 18:33 [PATCH 1/1] mvebu: fix end-of-array check Derek LaHousse
2022-12-04 7:17 ` [EXT] " Kostya Porotchkin
2022-12-04 10:39 ` Pali Rohár
2022-12-05 11:42 ` Stefan Roese
2022-12-05 18:18 ` Pali Rohár
2022-12-06 6:10 ` Stefan Roese
2022-12-06 19:56 ` Pali Rohár
2022-12-07 7:14 ` Stefan Roese
2022-12-04 21:16 ` Simon Glass
2022-12-04 21:51 ` Pali Rohár [this message]
2022-12-05 16:11 ` 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=20221204215103.bbmc3gko2haebs4m@pali \
--to=pali@kernel.org \
--cc=derek@seaofdirac.org \
--cc=kostap@marvell.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--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