From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/6] tools/nolibc: fix some undefined behaviour and enable UBSAN
Date: Fri, 18 Apr 2025 23:20:29 +0200 [thread overview]
Message-ID: <44ef9e15-d7dd-4079-93c1-5f9cf79d675b@t-8ch.de> (raw)
In-Reply-To: <acffaf72-aca5-4301-ade4-ea12571e4392@paulmck-laptop>
Hi Paul,
On 2025-04-18 10:32:27-0700, Paul E. McKenney wrote:
> On Wed, Apr 16, 2025 at 08:40:15PM +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>
>
> Thank you, Thomas! Are these intended to go into the current v6.15
> release, or are you instead thinking in terms of the v6.16 merge window?
> Either works for me, but left to myself, I would assume the v6.16
> merge window. ;-)
They are intended for v6.16 through the normal process.
Thomas
>
> > ---
> > Thomas Weißschuh (6):
> > tools/nolibc: add __nolibc_has_feature()
> > tools/nolibc: disable function sanitizer for _start_c()
> > tools/nolibc: properly align dirent buffer
> > tools/nolibc: fix integer overflow in i{64,}toa_r() and
> > selftests/nolibc: disable ubsan for smash_stack()
> > selftests/nolibc: enable UBSAN if available
> >
> > tools/include/nolibc/compiler.h | 6 ++++++
> > tools/include/nolibc/crt.h | 5 +++++
> > tools/include/nolibc/dirent.h | 1 +
> > tools/include/nolibc/stdlib.h | 24 ++++++++----------------
> > tools/testing/selftests/nolibc/Makefile | 3 ++-
> > tools/testing/selftests/nolibc/nolibc-test.c | 1 +
> > 6 files changed, 23 insertions(+), 17 deletions(-)
> > ---
> > base-commit: 7c73c10b906778384843b9d3ac6c2224727bbf5c
> > change-id: 20250416-nolibc-ubsan-028401698654
> >
> > Best regards,
> > --
> > Thomas Weißschuh <linux@weissschuh.net>
> >
next prev parent reply other threads:[~2025-04-18 21:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 18:40 Thomas Weißschuh
2025-04-16 18:40 ` [PATCH 1/6] tools/nolibc: add __nolibc_has_feature() Thomas Weißschuh
2025-04-16 18:40 ` [PATCH 2/6] tools/nolibc: disable function sanitizer for _start_c() Thomas Weißschuh
2025-04-19 9:06 ` Willy Tarreau
2025-04-19 10:10 ` Thomas Weißschuh
2025-04-19 10:27 ` Willy Tarreau
2025-04-16 18:40 ` [PATCH 3/6] tools/nolibc: properly align dirent buffer Thomas Weißschuh
2025-04-19 9:11 ` Willy Tarreau
2025-04-19 10:11 ` Thomas Weißschuh
2025-04-16 18:40 ` [PATCH 4/6] tools/nolibc: fix integer overflow in i{64,}toa_r() and Thomas Weißschuh
2025-04-19 9:40 ` Willy Tarreau
2025-04-19 10:26 ` Thomas Weißschuh
2025-04-16 18:40 ` [PATCH 5/6] selftests/nolibc: disable ubsan for smash_stack() Thomas Weißschuh
2025-04-16 18:40 ` [PATCH 6/6] selftests/nolibc: enable UBSAN if available Thomas Weißschuh
2025-04-19 9:41 ` Willy Tarreau
2025-04-18 17:32 ` [PATCH 0/6] tools/nolibc: fix some undefined behaviour and enable UBSAN Paul E. McKenney
2025-04-18 21:20 ` Thomas Weißschuh [this message]
2025-04-18 21:29 ` Paul E. McKenney
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=44ef9e15-d7dd-4079-93c1-5f9cf79d675b@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--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
all inboxes | Powered by JetHome®