From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/9] sandbox: use native setjmp/longjmp/initjmp implementation by default
Date: Thu, 28 Nov 2024 09:21:09 +0100 [thread overview]
Message-ID: <173278206963.3726006.3004031451155897300.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241125153523.1411849-1-a.fatoum@pengutronix.de>
On Mon, 25 Nov 2024 16:35:14 +0100, Ahmad Fatoum wrote:
> In order to implement initjmp, we have two ways with available
> functionality: The sigaltstack we are currently using and
> makecontext/swapcontext. makecontext/swapcontext are unfortunately
> deprecated in favor of POSIX threads and the sigaltstack runs afoul of
> AddressSanitizer when compiled with clang.
>
> This series fixes this by using the already existent assembly
> implementations
>
> [...]
Applied, thanks!
[1/9] sandbox: asm: support inclusion from sandbox os support code
https://git.pengutronix.de/cgit/barebox/commit/?id=ab213e2680da (link may not be stable)
[2/9] test: self: setjmp: add simple initial testcase
https://git.pengutronix.de/cgit/barebox/commit/?id=66036a7147bf (link may not be stable)
[3/9] sandbox: source/invoke um Makefiles provided by host architecture
https://git.pengutronix.de/cgit/barebox/commit/?id=9e8108599522 (link may not be stable)
[4/9] sandbox: setjmp: mark C version as __weak
https://git.pengutronix.de/cgit/barebox/commit/?id=ed8e28428731 (link may not be stable)
[5/9] sandbox: use native setjmp/longjmp/initjmp implementation by default
https://git.pengutronix.de/cgit/barebox/commit/?id=70559ef4a7a0 (link may not be stable)
[6/9] sandbox: retire HAVE_ARCH_ASAN
https://git.pengutronix.de/cgit/barebox/commit/?id=550d92229e8b (link may not be stable)
[7/9] bthread: move asan fiber API into header
https://git.pengutronix.de/cgit/barebox/commit/?id=ee81cbe355a2 (link may not be stable)
[8/9] test: self: setjmp: make compatible with ASAN
https://git.pengutronix.de/cgit/barebox/commit/?id=d253f23723d9 (link may not be stable)
[9/9] bthread: fix use of ASAN fiber stack switch API
https://git.pengutronix.de/cgit/barebox/commit/?id=e61fa7a37f18 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-11-28 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 15:35 Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 1/9] sandbox: asm: support inclusion from sandbox os support code Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 2/9] test: self: setjmp: add simple initial testcase Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 3/9] sandbox: source/invoke um Makefiles provided by host architecture Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 4/9] sandbox: setjmp: mark C version as __weak Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 5/9] sandbox: use native setjmp/longjmp/initjmp implementation by default Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 6/9] sandbox: retire HAVE_ARCH_ASAN Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 7/9] bthread: move asan fiber API into header Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 8/9] test: self: setjmp: make compatible with ASAN Ahmad Fatoum
2024-11-25 15:35 ` [PATCH 9/9] bthread: fix use of ASAN fiber stack switch API Ahmad Fatoum
2024-11-28 8:21 ` Sascha Hauer [this message]
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=173278206963.3726006.3004031451155897300.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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