From: Heiko Carstens <hca@linux.ibm.com>
To: Jens Remus <jremus@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [PATCH 0/2] s390/vdso: Fix GNU_EH_FRAME PHDR
Date: Fri, 10 Jul 2026 09:46:00 +0200 [thread overview]
Message-ID: <20260710074600.17568Beb-hca@linux.ibm.com> (raw)
In-Reply-To: <20260706151909.103539-1-jremus@linux.ibm.com>
On Mon, Jul 06, 2026 at 05:19:07PM +0200, Jens Remus wrote:
> Patch 1 fixes the empty GNU_EH_FRAME program table header entry to
> enable unwinders and stacktracers to locate the .eh_frame_hdr section.
>
> Patch 2 uses symbolic constants for the PHDR permission flags to improve
> readability and explicitly specifies the GNU_EH_FRAME PHDR to be read-
> only.
>
> Regards,
> Jens
>
>
> Jens Remus (2):
> s390/vdso: Pass --eh-frame-hdr to the linker
> s390/vdso: Use symbolic constants for the PHDR permission flags
>
> arch/s390/kernel/vdso/Makefile | 3 ++-
> arch/s390/kernel/vdso/vdso.lds.S | 12 ++++++++----
> 2 files changed, 10 insertions(+), 5 deletions(-)
This series is in limbo state. Do you plan to send a new version to
address the very minor nits, or should it stay as is?
In any case:
Acked-by: Heiko Carstens <hca@linux.ibm.com>
prev parent reply other threads:[~2026-07-10 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 15:19 [PATCH 0/2] s390/vdso: Fix GNU_EH_FRAME PHDR Jens Remus
2026-07-06 15:19 ` [PATCH 1/2] s390/vdso: Pass --eh-frame-hdr to the linker Jens Remus
2026-07-06 15:22 ` Jens Remus
2026-07-06 17:26 ` Ilya Leoshkevich
2026-07-06 15:19 ` [PATCH 2/2] s390/vdso: Use symbolic constants for the PHDR permission flags Jens Remus
2026-07-06 17:06 ` Ilya Leoshkevich
2026-07-07 7:32 ` Jens Remus
2026-07-10 7:46 ` Heiko Carstens [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=20260710074600.17568Beb-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox