From: Xi Ruoyao <xry111@xry111.site>
To: WANG Xuerui <i.swmail@xen0n.name>,
liuzhensong <liuzhensong@loongson.cn>,
binutils@sourceware.org
Cc: maskray@google.com, caiyinyu@loongson.cn, chenglulu@loongson.cn,
mengqinggang@loongson.cn, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Set defaults to exec stack 0.
Date: Mon, 25 Jul 2022 10:44:52 +0800 [thread overview]
Message-ID: <194be062c7812a604ff914b49caa1532d7bd85ed.camel@xry111.site> (raw)
In-Reply-To: <94ed682f-1b36-0fe1-7383-19657fa33468@xen0n.name>
On Mon, 2022-07-25 at 10:24 +0800, WANG Xuerui wrote:
> On 2022/7/25 10:22, liuzhensong wrote:
> > ---
> > bfd/elfnn-loongarch.c | 1 +
> > ld/testsuite/ld-elf/elf.exp | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/bfd/elfnn-loongarch.c b/bfd/elfnn-loongarch.c
> > index 4efe3d9370c..43182ead8cd 100644
> > --- a/bfd/elfnn-loongarch.c
> > +++ b/bfd/elfnn-loongarch.c
> > @@ -132,6 +132,7 @@ struct loongarch_elf_link_hash_table
> >
> > #define elf_backend_want_dynrelro 1
> > #define elf_backend_rela_normal 1
> > +#define elf_backend_default_execstack 0
> >
> > /* Generate a PLT header. */
> >
> > diff --git a/ld/testsuite/ld-elf/elf.exp b/ld/testsuite/ld-
> > elf/elf.exp
> > index 10c635e9593..b8829b4e3ee 100644
> > --- a/ld/testsuite/ld-elf/elf.exp
> > +++ b/ld/testsuite/ld-elf/elf.exp
> > @@ -187,6 +187,7 @@ proc target_defaults_to_execstack {} {
> > || [istarget "nios2*-*-*"]
> > || [istarget "powerpc64*-*-*"]
> > || [istarget "riscv*-*-*"]
> > + || [istarget "loongarch*-*-*"]
> > || [istarget "tilegx*-*-*"]
> > || [istarget "tilepro*-*-*"] } {
> > return 0
> Looks good to me. I don't know why this isn't the case from the
> beginning... I'll test on Gentoo shortly after.
I guess it's just noticed recently because ld has started to emit
warning for assembly inputs w/o .note.GNU-stack section. Before the
warning the only way to notice this problem is "process xxx is started
with executable stack" in the kernel log if someone forgot to add a
.note.GNU-stack section in the assembly source file.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-07-25 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 2:22 liuzhensong
2022-07-25 2:24 ` WANG Xuerui
2022-07-25 2:44 ` Xi Ruoyao [this message]
2022-07-25 7:51 ` Fangrui Song
2022-07-25 8:08 ` Andreas Schwab
2022-07-25 8:14 ` Xi Ruoyao
2022-07-25 8:35 ` Andreas Schwab
2022-07-25 9:17 ` WANG Xuerui
2022-07-25 9:18 ` Huacai Chen
2022-07-25 9:22 ` Xi Ruoyao
2022-07-25 9:44 ` WANG Xuerui
2022-07-30 19:20 ` WANG Xuerui
2022-08-01 1:10 ` liuzhensong
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=194be062c7812a604ff914b49caa1532d7bd85ed.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=caiyinyu@loongson.cn \
--cc=chenglulu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=liuzhensong@loongson.cn \
--cc=maskray@google.com \
--cc=mengqinggang@loongson.cn \
--cc=xuchenghua@loongson.cn \
/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).