From: Stefan Liebler <stli@linux.ibm.com>
To: libc-stable@sourceware.org
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: [COMMITTED 2.24 / 2.25 / 2.26 / 2.27 / 2.28] Fix segfault in maybe_script_execute.
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <5e61e2a6-c2a3-641d-3675-ff76bf2cdfe5@linux.ibm.com> (raw)
In-Reply-To: <E1A46E87-CE92-49F9-8535-C55B83C55C79@linaro.org>
Hi,
I've cherry picked the commit "Fix segfault in maybe_script_execute."
(https://sourceware.org/git/?p=glibc.git;a=commit;h=28669f86f6780a18daca264f32d66b1428c9c6f1)
and it is now available on glibc release branches 2.24 ... 2.28.
Bye
Stefan
On 09/07/2018 03:36 PM, Adhemerval Zanella wrote:
>
>
>> Il giorno 07 set 2018, alle ore 11:33, Stefan Liebler <stli@linux.ibm.com> ha scritto:
>>
>>> On 09/07/2018 09:57 AM, Adhemerval Zanella wrote:
>>> Thanks for the patch, could you check if we need to backport this fix to older releases as well?
>> As far as I've seen, maybe_script_execute was introduced with commit "posix: New Linux posix_spawn{p} implementation" (https://sourceware.org/git/?p=glibc.git;a=commit;h=9ff72da471a509a8c19791efe469f47fa6977410)
>> => first release was glibc 2.24.
>>
>> Should it be backported to all versions: glibc 2.24 ... 2.28?
>>
>
> Ideally yes, this is quite simple patch so I thin backport should not require extra work.
>
next parent reply other threads:[~2018-09-10 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fab031c-9748-42e4-7137-55bf9ae59545@linux.ibm.com>
[not found] ` <mvmd0tsf49k.fsf@suse.de>
[not found] ` <032ef9d4-c359-01ca-7af1-d66730f1d050@linux.ibm.com>
[not found] ` <mvmsh2ndn6t.fsf@suse.de>
[not found] ` <f69c7e70-b0b0-b635-1582-0a3ad36de981@linux.ibm.com>
[not found] ` <mvmo9dbdm33.fsf@suse.de>
[not found] ` <2ed9096b-245f-9ddb-164d-46e137568146@linux.ibm.com>
[not found] ` <mvmk1nyewzy.fsf@suse.de>
[not found] ` <8dfb9cfd-5a16-fbbc-cd29-39c9e0f210ef@linux.ibm.com>
[not found] ` <31085028-8624-428E-ACF2-8623CD3D44E1@linaro.org>
[not found] ` <3c29ecc1-d709-dc43-5720-c7c628c4177c@linux.ibm.com>
[not found] ` <E1A46E87-CE92-49F9-8535-C55B83C55C79@linaro.org>
2018-01-01 0:00 ` Stefan Liebler [this message]
2018-01-01 0:00 ` Adhemerval Zanella
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=5e61e2a6-c2a3-641d-3675-ff76bf2cdfe5@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).