public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Fangrui Song <i@maskray.me>,
	binutils@sourceware.org,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: PING: [PATCH] aarch64: Disallow copy relocations on protected data
Date: Wed, 22 Jun 2022 12:15:44 +0100	[thread overview]
Message-ID: <YrL54HZBuJcdR88Q@arm.com> (raw)
In-Reply-To: <6c42d40b-2939-b6fb-6d13-22058b2118bf@redhat.com>

The 06/22/2022 11:55, Nick Clifton wrote:
> Hi Fangrui,
> 
> > > > > >   bfd/elfnn-aarch64.c                           | 28 ++++++++++++++++++-
> > > > > >   ld/testsuite/ld-aarch64/aarch64-elf.exp       |  9 ++++++
> > > > > >   .../ld-aarch64/copy-reloc-protected.d         |  2 ++
> > > > > >   ld/testsuite/ld-aarch64/protected.s           |  8 ++++++
> 
> > Ping^2
> 
> Sorry - I thought that this patch had already been approved.
> 
> Patch approved - please apply.

i was waiting for the glibc side to decide how to deal with
this case.

but now all related patches are committed to glibc so this
can go in.

  reply	other threads:[~2022-06-22 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  5:10 Fangrui Song
2022-05-27 22:43 ` Fangrui Song
     [not found] ` <CAN30aBHDJM4KJAJJ_=4=vKgJL-yow2roUEUa7LFaAFaivkVswg@mail.gmail.com>
2022-06-01  5:53   ` PING: " Fangrui Song
     [not found]   ` <CAN30aBH68jT8ArEPEx_X-zVzuOmN3u_KV5HKc-Vgc2tVohJADw@mail.gmail.com>
2022-06-15 22:28     ` Fangrui Song
2022-06-21 19:27       ` Fangrui Song
     [not found]       ` <DS7PR12MB57658D646BB4944D4BECAF84CBB39@DS7PR12MB5765.namprd12.prod.outlook.com>
2022-06-22 10:55         ` Nick Clifton
2022-06-22 11:15           ` Szabolcs Nagy [this message]
2022-07-01 11:16             ` Matthias Klose

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=YrL54HZBuJcdR88Q@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=binutils@sourceware.org \
    --cc=i@maskray.me \
    --cc=nickc@redhat.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).