public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Eugene Loh <eugene.loh@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 3/5] test: Fix some ustackdepth tests
Date: Thu, 9 Oct 2025 17:11:26 -0400	[thread overview]
Message-ID: <45d166d3-7a33-ca9b-3da6-8eb66048835a@oracle.com> (raw)
In-Reply-To: <aOfjAfXbxsUP7aeM@oracle.com>

Hmm, yeah.  Okay, change posted as a new patch to apply on top of the 
older one.

On 10/9/25 12:29, Kris Van Hees wrote:
> This test seems to not work right if the system limit is already 200, 
> which
> it can be.  Perhaps it should first lower it to e.g. 20, then raise it to 200,
> and no matter what, restore the original value?

  reply	other threads:[~2025-10-09 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  6:24 [PATCH 1/5] test: Use a more ubiquitous probe for return()-action tests eugene.loh
2025-10-01  6:24 ` [PATCH 2/5] test: Adjust skip file for lockmem problem eugene.loh
2025-10-03  3:52   ` Kris Van Hees
2025-10-01  6:24 ` [PATCH 3/5] test: Fix some ustackdepth tests eugene.loh
2025-10-03  4:07   ` Kris Van Hees
2025-10-09 16:29     ` Kris Van Hees
2025-10-09 21:11       ` Eugene Loh [this message]
2025-10-01  6:24 ` [PATCH 4/5] test: Fix antiquated reference to dtrace_ustackdepth_max eugene.loh
2025-10-03  3:56   ` Kris Van Hees
2025-10-01  6:24 ` [PATCH 5/5] test: Remove antiquated special case for aarch64 eugene.loh
2025-10-03  3:55   ` Kris Van Hees
2025-10-03  3:50 ` [PATCH 1/5] test: Use a more ubiquitous probe for return()-action tests 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=45d166d3-7a33-ca9b-3da6-8eb66048835a@oracle.com \
    --to=eugene.loh@oracle.com \
    --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