From: Daniel Palmer <daniel@thingy.jp>
To: w@1wt.eu, linux@weissschuh.net
Cc: linux-kernel@vger.kernel.org, Daniel Palmer <daniel@thingy.jp>
Subject: [PATCH 0/2] Small stack protector bits
Date: Sat, 25 Apr 2026 20:13:13 +0900 [thread overview]
Message-ID: <20260425111315.3191461-1-daniel@thingy.jp> (raw)
Reworking my "static pie" series and going back
through comments from Willy and Thomas...
First patch was suggested by Willy as a preemptive
clean up task before the series. So here it is.
Second one is an issue only appeared with relocation
(because you shouldn't access global data before relocation)
but seems sensible to do.
Daniel Palmer (2):
tools/nolibc: Rename __no_stack_protector to
__nolibc_no_stack_protector
tools/nolibc: Don't use stack protector before setting it up
tools/include/nolibc/arch-arm.h | 2 +-
tools/include/nolibc/arch-arm64.h | 2 +-
tools/include/nolibc/arch-loongarch.h | 2 +-
tools/include/nolibc/arch-m68k.h | 2 +-
tools/include/nolibc/arch-mips.h | 2 +-
tools/include/nolibc/arch-powerpc.h | 8 ++++----
tools/include/nolibc/arch-riscv.h | 2 +-
tools/include/nolibc/arch-s390.h | 2 +-
tools/include/nolibc/arch-sh.h | 2 +-
tools/include/nolibc/arch-sparc.h | 2 +-
tools/include/nolibc/arch-x86.h | 4 ++--
tools/include/nolibc/compiler.h | 4 ++--
tools/include/nolibc/crt.h | 2 +-
tools/include/nolibc/stackprotector.h | 2 +-
14 files changed, 19 insertions(+), 19 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-25 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 11:13 Daniel Palmer [this message]
2026-04-25 11:13 ` [PATCH 1/2] tools/nolibc: Rename __no_stack_protector to __nolibc_no_stack_protector Daniel Palmer
2026-04-27 17:24 ` Thomas Weißschuh
2026-04-25 11:13 ` [PATCH 2/2] tools/nolibc: Don't use stack protector before setting it up Daniel Palmer
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=20260425111315.3191461-1-daniel@thingy.jp \
--to=daniel@thingy.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--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
all inboxes | Powered by JetHome®