From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: PING^1 [PATCH 2/2] Add run-time chesk for indirect external access
Date: Sun, 26 Sep 2021 19:10:19 -0700 [thread overview]
Message-ID: <CAMe9rOqYCu7-f+MgPC59tECkicoXUJwDpQrpX8sV0PbRYXtBPA@mail.gmail.com> (raw)
In-Reply-To: <20210803215914.4170913-2-hjl.tools@gmail.com>
On Tue, Aug 3, 2021 at 2:59 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> When performing symbol lookup for references in executable without
> indirect external access:
>
> 1. Disallow copy relocations in executable against protected data symbols
> in a shared object with indirect external access.
> 2. Disallow non-zero symbol values of undefined function symbols in
> executable, which are used as the function pointer, against protected
> function symbols in a shared object with indirect external access.
PING:
https://sourceware.org/pipermail/libc-alpha/2021-August/129798.html
https://sourceware.org/pipermail/libc-alpha/2021-August/129799.html
--
H.J.
next prev parent reply other threads:[~2021-09-27 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 21:59 [PATCH 1/2] Initial support for GNU_PROPERTY_1_NEEDED H.J. Lu via Libc-alpha
2021-08-03 21:59 ` [PATCH 2/2] Add run-time chesk for indirect external access H.J. Lu via Libc-alpha
2021-09-27 2:10 ` H.J. Lu via Libc-alpha [this message]
2021-10-07 16:58 ` Adhemerval Zanella via Libc-alpha
2021-10-07 17:10 ` H.J. Lu via Libc-alpha
2021-10-07 17:45 ` Adhemerval Zanella via Libc-alpha
2021-10-07 14:53 ` [PATCH 1/2] Initial support for GNU_PROPERTY_1_NEEDED Adhemerval Zanella via Libc-alpha
2021-10-07 15:11 ` H.J. Lu via Libc-alpha
2021-10-07 16:53 ` Adhemerval Zanella via Libc-alpha
2021-10-07 17:04 ` H.J. Lu via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMe9rOqYCu7-f+MgPC59tECkicoXUJwDpQrpX8sV0PbRYXtBPA@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=hjl.tools@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).