From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,kernel@pengutronix.de,kees@kernel.org,andy@kernel.org,jre@pengutronix.de,akpm@linux-foundation.org
Subject: [to-be-updated] lib-tests-string_helpers-check-null-terminator-too.patch removed from -mm tree
Date: Tue, 06 Oct 2026 19:00:02 -0700 [thread overview]
Message-ID: <20261007020004.508ED1F0089E@smtp.kernel.org> (raw)
The quilt patch titled
Subject: lib/tests: string_helpers: check null terminator too
has been removed from the -mm tree. Its filename was
lib-tests-string_helpers-check-null-terminator-too.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: Jonas Rebmann <jre@pengutronix.de>
Subject: lib/tests: string_helpers: check null terminator too
Date: Wed, 16 Sep 2026 19:38:06 +0200
Patch series "lib/string_helpers: fixes and test cases for
string_unescape()".
This series fixes two bugs in string_unescape() regarding the destination
buffer length. Both fixes are accompanied with kunit tests which would
fail without the fixes.
To make this possible, preparatory patches 1 and 2 improve and clean up
testing helpers and 3 introduces test_unescape_one() which allows for
targeted testing of the string_unescape() function.
This patch (of 5):
string_unescape() returns the number of character written to dst, not
counting the null terminator which is always written.
Ensure string_unescape has included the null terminator by adding a
separate check.
While at it, improve output for failed tests by showing the memory dump
even if the length differs.
Link: https://lore.kernel.org/20260916-string_unescape-v1-0-7f8bd986fa33@pengutronix.de
Link: https://lore.kernel.org/20260916-string_unescape-v1-1-7f8bd986fa33@pengutronix.de
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Shevchenko <andy@kernel.org>
Cc: Kees Cook <kees@kernel.org>
Cc: Sascha Hauer <kernel@pengutronix.de>
---
lib/tests/string_helpers_kunit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/lib/tests/string_helpers_kunit.c~lib-tests-string_helpers-check-null-terminator-too
+++ a/lib/tests/string_helpers_kunit.c
@@ -22,7 +22,7 @@ static void test_string_check_buf(struct
char *out_real, size_t q_real,
char *out_test, size_t q_test)
{
- KUNIT_ASSERT_EQ_MSG(test, q_real, q_test, "name:%s", name);
+ KUNIT_EXPECT_EQ_MSG(test, q_real, q_test, "name:%s", name);
KUNIT_EXPECT_MEMEQ_MSG(test, out_test, out_real, q_test,
"name:%s", name);
}
@@ -103,6 +103,7 @@ static void test_string_unescape(struct
test_string_check_buf(test, name, flags, in, p - 1, out_real, q_real,
out_test, q_test);
+ KUNIT_EXPECT_EQ_MSG(test, out_real[q_real], '\0', "name:%s", name);
}
struct test_string_1 {
_
Patches currently in -mm which might be from jre@pengutronix.de are
lib-tests-string_helpers-drop-unused-parameters.patch
lib-tests-string_helpers-introduce-test_string_unescape_one.patch
lib-string_helpers-use-full-destination-buffer-in-string_unescape.patch
lib-string_helpers-fix-counting-of-remaining-bytes-in-string_unescape.patch
reply other threads:[~2026-10-07 2:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261007020004.508ED1F0089E@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=jre@pengutronix.de \
--cc=kees@kernel.org \
--cc=kernel@pengutronix.de \
--cc=mm-commits@vger.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.