From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Subject: [PATCH v2 0/3] A few backlogged fixes, and a crash bug
Date: Tue, 10 Jan 2023 13:00:47 +0000 [thread overview]
Message-ID: <20230110130050.366404-1-nick.alcock@oracle.com> (raw)
This is the same as the built-up patch series I sent in mid-December,
but without the stalled libtool fixes still awaiting review. In
addition, this fixes a crash bug recently spotted on 32-bit Linux (and
possible, though not terribly likely, on any platform when CTF is linked
together). Since the crash involves accessing and then (if you're
unlucky) modifying memory out of bounds, I consider it important enough to
backport to every branch with the affected code: 2.36 and later.
The usual test cycle is ongoing. No failures anywhere yet. The testsuite
is now additionally being run on the compile farm i686-pc-linux-gnu
system that reliably reproduces the overrun bug, and with
MALLOC_PERTURB_ set, though since that doesn't perturb never-used memory
I don't expect it to reliably detect that bug on its own.
Nick Alcock (3):
ctf: fix various dreadful typos in the ctf_archive format comments
libctf: skip the testsuite from inside dejagnu
libctf: ctf-link outdated input check faulty
include/ctf.h | 8 +--
libctf/Makefile.am | 3 +-
libctf/Makefile.in | 95 +++++++++++++----------------
libctf/configure | 21 +++----
libctf/configure.ac | 7 ++-
libctf/ctf-link.c | 35 +++++++++--
libctf/testsuite/config/default.exp | 5 ++
7 files changed, 94 insertions(+), 80 deletions(-)
--
2.39.0.267.g7648178303
next reply other threads:[~2023-01-10 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:00 Nick Alcock [this message]
2023-01-10 13:00 ` [PATCH v2 1/3] ctf: fix various dreadful typos in the ctf_archive format comments Nick Alcock
2023-01-10 13:00 ` [PATCH v2 2/3] libctf: skip the testsuite from inside dejagnu Nick Alcock
2023-01-10 13:00 ` [PATCH v2 3/3] libctf: ctf-link outdated input check faulty Nick Alcock
2023-01-11 17:21 ` [PATCH 2.40 " Nick Alcock
2023-01-12 13:43 ` Nick Clifton
2023-01-12 14:46 ` Nick Alcock
2023-01-12 15:39 ` Nick Alcock
2023-01-13 11:14 ` Nick Clifton
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=20230110130050.366404-1-nick.alcock@oracle.com \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).