From: Tomas Dzik via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] Fix to float_trigo core dump and related enhancements
Date: Thu, 9 Jul 2026 17:40:03 +0200 [thread overview]
Message-ID: <cover.1783610933.git.tdzik@redhat.com> (raw)
Hi all,
following 3 patches fix a core dump we observed during testing. Because
failed malloc() was contributing factor to it I added also some checks
to malloc() return value. And since I was editing these files I spotted
that they use sprintf() and I replaced it with snprintf() which is IMHO
safer and can make debugging test failures easier.
I would be grateful for review.
Best regards,
Tomas D.
Tomas Dzik (3):
LTP/Lite test float_trigo core dumps due to free(): invalid pointer
Add some checks for malloc() returning NULL
Replace sprintf() with more secure snprintf() variant in float tests
testcases/misc/math/float/bessel/genbessel.c | 10 +++---
.../misc/math/float/exp_log/genexp_log.c | 24 +++++++++----
testcases/misc/math/float/iperb/geniperb.c | 10 ++++--
testcases/misc/math/float/main.c | 18 +++++++---
testcases/misc/math/float/power/genpower.c | 21 ++++++++----
testcases/misc/math/float/thread_code.c | 34 +++++++++++++------
testcases/misc/math/float/trigo/gentrigo.c | 24 +++++++++----
7 files changed, 99 insertions(+), 42 deletions(-)
--
2.55.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-07-09 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:40 Tomas Dzik via ltp [this message]
2026-07-09 15:40 ` [LTP] [PATCH 1/3] LTP/Lite test float_trigo core dumps due to free(): invalid pointer Tomas Dzik via ltp
2026-07-09 16:34 ` [LTP] " linuxtestproject.agent
2026-07-09 15:40 ` [LTP] [PATCH 2/3] Add some checks for malloc() returning NULL Tomas Dzik via ltp
2026-07-09 15:40 ` [LTP] [PATCH 3/3] Replace sprintf() with more secure snprintf() variant in float tests Tomas Dzik via ltp
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=cover.1783610933.git.tdzik@redhat.com \
--to=ltp@lists.linux.it \
--cc=tdzik@redhat.com \
/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