From: Dragan Mladjenovic <dmladjenovic@wavecomp.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
"libc-stable@sourceware.org" <libc-stable@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
Siddhesh Poyarekar <siddhesh@sourceware.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: Re: Backport of mips: Force RWX stack for hard-float builds that can run on pre-4.8 kernels
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <5DBB1083.20301@wavecomp.com> (raw)
In-Reply-To: <4942384b-3d97-57c5-0e26-3cfebb4c755d@linaro.org>
On 04.09.2019. 21:32, Adhemerval Zanella wrote:
>
>
> On 04/09/2019 09:27, Dragan Mladjenovic wrote:
>>
>> On 28.08.2019. 19:35, Dragan Mladjenovic wrote:
>>> Hello everybody,
>>>
>>> Not sure if this is the right procedure, but I wish to propose the
>>> back-porting of [1] to most of the active release branches. You can find
>>> more info about the patch on [2]. The patch applies cleanly
>>> (sans the ChangeLog) up to 2.24 where it expects [3] from 2.25.
>>> I've attached both versions for reference.
>>> Checked for o32 hard-float and soft-float (where available) builds.
>>>
>>> Best regards,
>>> Dragan
>>>
>>>
>>> [1]
>>> https://sourceware.org/git/?p=glibc.git;a=commit;h=33bc9efd91de1b14354291fc8ebd5bce96379f12
>>>
>>> [2] https://sourceware.org/ml/libc-alpha/2019-08/msg00479.html
>>> [3]
>>> https://sourceware.org/git/?p=glibc.git;a=commit;h=7672e712e1cd91a9252bb9db8ac1d9b528e19f2e
>>>
>>
>> Did I made the mistake by not tying the original submission to a
>> bugzilla issue? Is the patch still eligible for backporting as it is, or
>> do I need to do something further?
>
> I don't have a strong opinion about backporting it, it seems to fall
> on the expected criteria of no new or compat symbols so it should not
> be a problem. It would be good to at least check the releases on a
> kernel higher than 4.8 so check if everything is ok.
>
Hi,
Sorry for this really late response. I finally managed to get my test
machines in order. If it helps, I rechecked old releases and patched
ones on 5.3 kernel /-hard-float/-EB/-mabi=o32/n32/n64 w/ and w/o
exec-stack by default and there were no new failures. What do I do next?
Do I need to get the approval of release manager for each branch
individually?
Best regards,
Dragan
next prev parent reply other threads:[~2019-10-31 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Dragan Mladjenovic
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic [this message]
2019-01-01 0:00 ` Florian Weimer
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic
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=5DBB1083.20301@wavecomp.com \
--to=dmladjenovic@wavecomp.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=ldv@altlinux.org \
--cc=libc-stable@sourceware.org \
--cc=siddhesh@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).