From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/7] tools/nolibc: fix some undefined behaviour and enable UBSAN
Date: Sat, 19 Apr 2025 13:30:55 +0200 [thread overview]
Message-ID: <20250419113055.GA2932@1wt.eu> (raw)
In-Reply-To: <20250419-nolibc-ubsan-v2-0-060b8a016917@weissschuh.net>
On Sat, Apr 19, 2025 at 12:46:17PM +0200, Thomas Weißschuh wrote:
> Fix some issues uncovered by UBSAN and enable UBSAN for nolibc-test to
> avoid regressions.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Changes in v2:
> - Introduce and use __nolibc_aligned_as()
> - Reduce size of fixes to i{64,}toa_r()
> - Link to v1: https://lore.kernel.org/r/20250416-nolibc-ubsan-v1-0-c4704bb23da7@weissschuh.net
Wow that was a fast turn-around! Looks good. For the whole series:
Acked-by: Willy Tarreau <w@1wt.eu>
Thank you Thomas!
Willy
prev parent reply other threads:[~2025-04-19 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 10:46 [PATCH v2 0/7] tools/nolibc: fix some undefined behaviour and enable UBSAN Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 1/7] tools/nolibc: add __nolibc_has_feature() Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 2/7] tools/nolibc: add __nolibc_aligned() and __nolibc_aligned_as() Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 3/7] tools/nolibc: disable function sanitizer for _start_c() Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 4/7] tools/nolibc: properly align dirent buffer Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 5/7] tools/nolibc: fix integer overflow in i{64,}toa_r() and Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 6/7] selftests/nolibc: disable ubsan for smash_stack() Thomas Weißschuh
2025-04-19 10:46 ` [PATCH v2 7/7] selftests/nolibc: enable UBSAN if available Thomas Weißschuh
2025-04-19 11:30 ` Willy Tarreau [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=20250419113055.GA2932@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.