Linux DTrace development list
 help / color / mirror / Atom feed
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 14/20] test: detect strlen corruption of strtab rodata and zeros
Date: Fri, 06 Nov 2026 13:10:01 +0000	[thread overview]
Message-ID: <87se1ertqu.fsf@esperi.org.uk> (raw)
In-Reply-To: <9a6be1ae2acce8402d1cf79e4a2e7b42@oracle.com>

On 30 Oct 2026, Kris Van Hees verbalised:

> + * ASSERTION: strlen() must not overwrite the IPv6 lookup table in the
> + *            rodata block of the strtab map.

... I'm not surprised you didn't spot this. Who would expect a strlen to
overwrite anything? But now it works via dt_bpf_probe_read_str, it's
writing into (a temporary entry in) the strtab as a side-effect, with a
STRSZ max...

-- 
NULL && (void)

  reply	other threads:[~2026-11-06 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 19:36 [PATCH 14/20] test: detect strlen corruption of strtab rodata and zeros Kris Van Hees
2026-11-06 13:10 ` Nick Alcock [this message]
2026-11-06 13:14   ` Nick Alcock
2026-11-06 21:26   ` Kris Van Hees

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=87se1ertqu.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