linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 0/6] tools/nolibc: add stackprotector support for more architectures
Date: Mon, 17 Apr 2023 18:01:30 +0200	[thread overview]
Message-ID: <20230408-nolibc-stackprotector-archs-v1-0-271f5c859c71@weissschuh.net> (raw)

Add stackprotector support for all remaining architectures, except s390.

On s390 the stackprotectors are not supported in "global" mode; only
"sysreg" mode which is not suppored in nolibc.

The series also contains a small optimization to strace output during
execution of nolibc-test.

This series is based on the 20230415-nolibc-updates-4a branch of the
nolibc tree.

Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Thomas Weißschuh (6):
      selftests/nolibc: reduce syscalls during space padding
      tools/nolibc: riscv: add stackprotector support
      tools/nolibc: aarch64: add stackprotector support
      tools/nolibc: arm: add stackprotector support
      tools/nolibc: loongarch: add stackprotector support
      tools/nolibc: mips: add stackprotector support

 tools/include/nolibc/arch-aarch64.h          |  7 ++++++-
 tools/include/nolibc/arch-arm.h              |  7 ++++++-
 tools/include/nolibc/arch-loongarch.h        |  7 ++++++-
 tools/include/nolibc/arch-mips.h             |  8 +++++++-
 tools/include/nolibc/arch-riscv.h            |  7 ++++++-
 tools/testing/selftests/nolibc/Makefile      |  5 +++++
 tools/testing/selftests/nolibc/nolibc-test.c | 15 +++++++++++----
 7 files changed, 47 insertions(+), 9 deletions(-)
---
base-commit: e35214ea9db7477a02e67a8b412e8046534bb97c
change-id: 20230408-nolibc-stackprotector-archs-42244674616e

Best regards,
-- 
Thomas Weißschuh <linux@weissschuh.net>


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2023-04-17 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 16:01 Thomas Weißschuh [this message]
2023-04-17 16:01 ` [PATCH 1/6] selftests/nolibc: reduce syscalls during space padding Thomas Weißschuh
2023-04-17 16:01 ` [PATCH 2/6] tools/nolibc: riscv: add stackprotector support Thomas Weißschuh
2023-04-17 19:35   ` Palmer Dabbelt
2023-04-17 16:01 ` [PATCH 3/6] tools/nolibc: aarch64: " Thomas Weißschuh
2023-04-17 16:01 ` [PATCH 4/6] tools/nolibc: arm: " Thomas Weißschuh
2023-04-17 16:01 ` [PATCH 5/6] tools/nolibc: loongarch: " Thomas Weißschuh
2023-04-17 16:01 ` [PATCH 6/6] tools/nolibc: mips: " Thomas Weißschuh

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=20230408-nolibc-stackprotector-archs-v1-0-271f5c859c71@weissschuh.net \
    --to=linux@weissschuh.net \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    /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).