From: Richard Weinberger <richard@nod.at>
To: davidgow <davidgow@google.com>
Cc: anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Nick Desaulniers <ndesaulniers@google.com>,
tglx <tglx@linutronix.de>, mingo <mingo@redhat.com>,
dave hansen <dave.hansen@linux.intel.com>,
torvalds <torvalds@linux-foundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
Daniel Latypov <dlatypov@google.com>,
linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kunit-dev <kunit-dev@googlegroups.com>, x86 <x86@kernel.org>,
Lukas Straub <lukasstraub2@web.de>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2] arch: um: Mark the stack non-executable to fix a binutils warning
Date: Wed, 21 Sep 2022 09:14:23 +0200 (CEST) [thread overview]
Message-ID: <290835862.246902.1663744463482.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20220921064855.2841607-1-davidgow@google.com>
----- Ursprüngliche Mail -----
> Von: "davidgow" <davidgow@google.com>
>
> Changes since v1:
> http://lists.infradead.org/pipermail/linux-um/2022-August/004234.html
> - Pass the -z noexecstack and --no-warn-rwx-segments flags as LDFLAGS,
> rather than as CFLAGS via -Wl
> - Check that --no-warn-rwx-segments exists with the ld-option function
> (Thanks Richard)
> - Add Lukas and Randy's tags.
Now it passes the test. :)
Applied.
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2022-09-21 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:48 [PATCH v2] arch: um: Mark the stack non-executable to fix a binutils warning David Gow
2022-09-21 7:14 ` Richard Weinberger [this message]
2022-09-21 17:47 ` Nick Desaulniers
2022-09-22 4:42 ` David Gow
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=290835862.246902.1663744463482.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=brendan.higgins@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=johannes@sipsolutions.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lukasstraub2@web.de \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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).