From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] Need -w for destructive actions, even if clause is not used
Date: Fri, 1 Aug 2025 14:19:06 -0400 [thread overview]
Message-ID: <aI0FGgbkNNq6yyQu@oracle.com> (raw)
In-Reply-To: <242f4ff5-c88b-ec46-de07-a6afc60936b9@oracle.com>
On Fri, Aug 01, 2025 at 02:02:27PM -0400, Eugene Loh wrote:
> On 8/1/25 13:49, Kris Van Hees wrote:
>
> > On Fri, Aug 01, 2025 at 11:36:17AM -0400, Kris Van Hees wrote:
> > > On Fri, Jul 11, 2025 at 12:40:24AM -0400, eugene.loh@oracle.com wrote:
> > > > From: Eugene Loh <eugene.loh@oracle.com>
> > > >
> > > > If a clause includes a destructive action but -w is not used, dtrace
> > > > should not start up, even if the clause is ignored (due to -Z).
> > > > Solaris treated this as a runtime error. We should do the same.
> > > >
> > > > The test err.Z_no-w.sh was misguided and is replaced by a more
> > > > direct test.
> > > >
> > > > delete mode 100644 test/unittest/usdt/err.Z_no-w.r
> > > > delete mode 100755 test/unittest/usdt/err.Z_no-w.sh
> > Why did you delete this test? Isn't it still a valid test anyway, and since
> > it tests this in a more practical sense, it seems to have value.
>
> The test was failing consistently on every platform; it was based on
> assumptions that were eventually discarded. So, no, not a valid test. It
> assumed behavior different from what this commit message asserts.
Ah, overlooked that it was testing for the non-compatible behaviour. OK.
next prev parent reply other threads:[~2025-08-01 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 4:40 [PATCH] Need -w for destructive actions, even if clause is not used eugene.loh
2025-07-15 10:59 ` Nick Alcock
2025-07-17 16:37 ` Eugene Loh
2025-07-22 13:36 ` Nick Alcock
2025-08-01 15:36 ` Kris Van Hees
2025-08-01 17:49 ` Kris Van Hees
2025-08-01 18:02 ` Eugene Loh
2025-08-01 18:19 ` Kris Van Hees [this message]
2025-08-01 18:15 ` Eugene Loh
2025-08-01 18:22 ` 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=aI0FGgbkNNq6yyQu@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.