From: Warner Losh <imp@bsdimp.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
Laurent Vivier <laurent@vivier.eu>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] linux-user: preserve incoming order of environment variables in the target
Date: Wed, 29 Mar 2023 16:06:40 +0200 [thread overview]
Message-ID: <CANCZdfpMtWtXfCWy_2S-PedFgayLHh_zW--aBUBc-m7uZ8988g@mail.gmail.com> (raw)
In-Reply-To: <ZCREaEiPyzYogkFj@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
On Wed, Mar 29, 2023, 4:00 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Wed, Mar 29, 2023 at 03:55:13PM +0200, Andreas Schwab wrote:
> > Do not reverse the order of environment variables in the target environ
> > array relative to the incoming environ order. Some testsuites depend on
> a
> > specific order, even though it is not defined by any standard.
> >
> > Signed-off-by: Andreas Schwab <schwab@suse.de>
> > ---
> > linux-user/main.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
>
> bsd-user/main.c appears to have an identical code pattern that
> will need the same fix
>
Agreed. I am finishing up a vacation but was going to check on this... I
agree that bsd-user wants to do this too...
Warner
>
> > diff --git a/linux-user/main.c b/linux-user/main.c
> > index 4b18461969..dbfd3ee8f1 100644
> > --- a/linux-user/main.c
> > +++ b/linux-user/main.c
> > @@ -691,7 +691,13 @@ int main(int argc, char **argv, char **envp)
> > envlist = envlist_create();
> >
> > /* add current environment into the list */
> > + /* envlist_setenv adds to the front of the list; to preserve environ
> > + order add from back to front */
> > for (wrk = environ; *wrk != NULL; wrk++) {
> > + continue;
> > + }
> > + while (wrk != environ) {
> > + wrk--;
> > (void) envlist_setenv(envlist, *wrk);
> > }
> >
> > --
> > 2.40.0
> >
> >
> > --
> > Andreas Schwab, SUSE Labs, schwab@suse.de
> > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
> > "And now for something completely different."
> >
>
> With regards,
> Daniel
> --
> |: https://berrange.com -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o-
> https://www.instagram.com/dberrange :|
>
>
>
[-- Attachment #2: Type: text/html, Size: 3428 bytes --]
prev parent reply other threads:[~2023-03-29 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:55 [PATCH v2] linux-user: preserve incoming order of environment variables in the target Andreas Schwab
2023-03-29 14:00 ` Daniel P. Berrangé
2023-03-29 14:02 ` Philippe Mathieu-Daudé
2023-03-29 14:53 ` Andreas Schwab
2023-03-29 14:04 ` Andreas Schwab
2023-03-29 14:12 ` Daniel P. Berrangé
2023-03-29 14:06 ` Warner Losh [this message]
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=CANCZdfpMtWtXfCWy_2S-PedFgayLHh_zW--aBUBc-m7uZ8988g@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=berrange@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=schwab@suse.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;
as well as URLs for NNTP newsgroup(s).