From: Andrew Jones <andrew.jones@linux.dev>
To: Thomas Huth <thuth@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
linux-s390@vger.kernel.org, "Nico Böhr" <nrb@linux.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
kvm@vger.kernel.org, "David Hildenbrand" <david@redhat.com>,
kvmarm@lists.linux.dev, "Paolo Bonzini" <pbonzini@redhat.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [kvm-unit-tests PATCH 0/2] Rework LDFLAGS and link with noexecstack
Date: Fri, 23 Jun 2023 16:46:25 +0200 [thread overview]
Message-ID: <20230623-7e80827ee6c29678c4da2c3f@orel> (raw)
In-Reply-To: <20230623125416.481755-1-thuth@redhat.com>
On Fri, Jun 23, 2023 at 02:54:14PM +0200, Thomas Huth wrote:
> I noticed that the latest version of ld (in Fedora rawhide) emits
> a warning on x86 and s390x, complaining about missing .note.GNU-stack
> section that implies an executable stack. It can be silenced by
> linking with "-z noexecstack".
>
> While trying to add this switch globally to the kvm-unit-tests, I
> had to discover that the common LDFLAGS are hardly used anywhere,
> so the first patch cleans up that problem first before adding the
> new flag in the second patch.
>
> Thomas Huth (2):
> Rework the common LDFLAGS to become more useful again
> Link with "-z noexecstack" to avoid warning from newer versions of ld
>
> Makefile | 2 +-
> arm/Makefile.common | 2 +-
> powerpc/Makefile.common | 2 +-
> s390x/Makefile | 2 +-
> x86/Makefile.common | 4 ++--
> 5 files changed, 6 insertions(+), 6 deletions(-)
>
> --
> 2.39.3
>
For the series
Reviewed-by: Andrew Jones <andrew.jones@linux.dev>
prev parent reply other threads:[~2023-06-23 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:54 [kvm-unit-tests PATCH 0/2] Rework LDFLAGS and link with noexecstack Thomas Huth
2023-06-23 12:54 ` [kvm-unit-tests PATCH 1/2] Rework the common LDFLAGS to become more useful again Thomas Huth
2023-06-23 12:54 ` [kvm-unit-tests PATCH 2/2] Link with "-z noexecstack" to avoid warning from newer versions of ld Thomas Huth
2023-06-23 14:24 ` Sean Christopherson
2023-06-23 16:03 ` Thomas Huth
2023-06-26 22:34 ` Sean Christopherson
2023-08-14 10:15 ` Thomas Huth
2023-06-23 14:46 ` Andrew Jones [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=20230623-7e80827ee6c29678c4da2c3f@orel \
--to=andrew.jones@linux.dev \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=thuth@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 NNTP newsgroup(s).