From: Sasha Levin <sashal@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Laurent Vivier <laurent@vivier.eu>,
YunQiang Su <ysu@wavecomp.com>, Helge Deller <deller@gmx.de>
Subject: Re: Please apply commit 2347961b11d4 ("binfmt_misc: pass binfmt_misc flags to the interpreter") to 5.10.y and later
Date: Thu, 4 Mar 2021 15:55:48 -0500 [thread overview]
Message-ID: <YEFJVENyU9QaO/NK@sashalap> (raw)
In-Reply-To: <YD42Sh5n2sjF9tNj@eldamar.lan>
On Tue, Mar 02, 2021 at 01:57:46PM +0100, Salvatore Bonaccorso wrote:
>Hi
>
>2347961b11d4 ("binfmt_misc: pass binfmt_misc flags to the
>interpreter") was applied in mainline and included in 5.12-rc1.
>
>Probably you could argue here on both a bugfix or feature addition.
>
>My intention is the following: In the Debian bugreport
>https://bugs.debian.org/970460 an issue was raised with qemu-user
>which needs to know if it has to preserve the argv[0]. As shown there
>it is an issue with multi-call binaries.
>
>So again, not sure if you want to consider it, but defintively
>Yunqiang Su and others would appreicate. If it gets backported we will
>pick it up automatically.
Given it needs changes in userspace too I'm not sure it qulifies as a
fix per-se. Though as you point out, it's really borderline.
Generally I would just take it, but it affects interactions with
userspace, so I feel less comfortable with this.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-03-04 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 12:57 Please apply commit 2347961b11d4 ("binfmt_misc: pass binfmt_misc flags to the interpreter") to 5.10.y and later Salvatore Bonaccorso
2021-03-04 20:55 ` Sasha Levin [this message]
2021-03-05 10:30 ` Greg Kroah-Hartman
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=YEFJVENyU9QaO/NK@sashalap \
--to=sashal@kernel.org \
--cc=carnil@debian.org \
--cc=deller@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=laurent@vivier.eu \
--cc=stable@vger.kernel.org \
--cc=ysu@wavecomp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.