public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v1] s390x: explicitly mark stack as not executable
Date: Wed, 9 Aug 2023 12:38:22 +0200	[thread overview]
Message-ID: <20230809123822.42475ce7@p-imbrenda> (raw)
In-Reply-To: <20230809091717.1549-1-nrb@linux.ibm.com>

On Wed,  9 Aug 2023 11:17:08 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:

> With somewhat recent GCC versions, we get this warning on s390x:
> 
>   /usr/bin/ld: warning: s390x/cpu.o: missing .note.GNU-stack section implies executable stack
>   /usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
> 
> We don't really care whether stack is executable or not since we set it
> up ourselves and we're running DAT off mostly anyways.
> 
> Silence the warning by explicitly marking the stack as not executable.
> 
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>

Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>

> ---
>  s390x/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/s390x/Makefile b/s390x/Makefile
> index 706be7920406..afa47ccbeb93 100644
> --- a/s390x/Makefile
> +++ b/s390x/Makefile
> @@ -79,7 +79,7 @@ CFLAGS += -O2
>  CFLAGS += -march=zEC12
>  CFLAGS += -mbackchain
>  CFLAGS += -fno-delete-null-pointer-checks
> -LDFLAGS += -nostdlib -Wl,--build-id=none
> +LDFLAGS += -nostdlib -Wl,--build-id=none -z noexecstack
>  
>  # We want to keep intermediate files
>  .PRECIOUS: %.o %.lds


  reply	other threads:[~2023-08-09 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09  9:17 [kvm-unit-tests PATCH v1] s390x: explicitly mark stack as not executable Nico Boehr
2023-08-09 10:38 ` Claudio Imbrenda [this message]
2023-08-13  9:50 ` Thomas Huth
2023-09-04  6:40   ` Nico Boehr

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=20230809123822.42475ce7@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.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