From: Nick Alcock <nix@esperi.org.uk>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 08/20] libdtrace: grow module address ranges geometrically
Date: Fri, 06 Nov 2026 12:54:55 +0000 [thread overview]
Message-ID: <87ik2at90g.fsf@esperi.org.uk> (raw)
In-Reply-To: <aa68020442985d905ffea22f1039e4eb@oracle.com>
On 30 Oct 2026, Kris Van Hees verbalised:
> ---
> libdtrace/dt_impl.h | 2 ++
> libdtrace/dt_module.c | 21 +++++++++++++++------
> 2 files changed, 17 insertions(+), 6 deletions(-)
I honestly thought we were already doing this.
Reviewed-by: Nick Alcock <nix@esperi.org.uk>
> - new_range = realloc(*range, sizeof(struct dtrace_addr_range) *
> - (*size+1));
Ew. I am ashamed (though addr ranges are rare enough that it's probably
not *disastrous*, it's not good).
--
NULL && (void)
prev parent reply other threads:[~2026-11-06 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:36 [PATCH 08/20] libdtrace: grow module address ranges geometrically Kris Van Hees
2026-11-06 12:54 ` Nick Alcock [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=87ik2at90g.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.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