From: Nick Alcock <nick.alcock@oracle.com>
To: "eugene.loh--- via DTrace-devel" <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, eugene.loh@oracle.com
Subject: Re: [DTrace-devel] [PATCH 13/14] Test: caller and stackdepth tests for io provider
Date: Fri, 13 Jun 2025 15:56:36 +0100 [thread overview]
Message-ID: <87a56bbsgr.fsf@esperi.org.uk> (raw)
In-Reply-To: <20250522180118.27343-13-eugene.loh@oracle.com> (eugene loh's message of "Thu, 22 May 2025 14:01:17 -0400")
On 22 May 2025, eugene loh spake thusly:
> From: Eugene Loh <eugene.loh@oracle.com>
>
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
> --- /dev/null
> +++ b/test/unittest/variables/bvar/tst.caller-io.sh
> @@ -0,0 +1,37 @@
> +#!/bin/bash
> +#
> +# Oracle Linux DTrace.
> +# Copyright (c) 2025, Oracle and/or its affiliates. All rights reserved.
> +# Licensed under the Universal Permissive License v 1.0 as shown at
> +# http://oss.oracle.com/licenses/upl.
> +
> +dtrace=$1
> +nblocks=1024
> +filesize=$((1024*$nblocks))
> +fsoptions="defaults,atime,diratime,nosuid,nodev"
> +iodir=$tmpdir/tst-caller-io.$$
> +tempfile=`mktemp -u -p $iodir`
> +
> +trap "umount $iodir; rmdir $iodir; rm -f $iodir.img" QUIT EXIT
> +
> +# create loopback file system
We have quite a lot of these I/O-trigger filesystem things now (this is
our sixth and seventh). Maybe we should think about refactoring the
mount-and-mkfs-and-dd-and-umount bit out into shared code at some
point...
--
NULL && (void)
next prev parent reply other threads:[~2025-06-13 14:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 18:01 [PATCH 01/14] Fix stack-skip counts for caller and stackdepth eugene.loh
2025-05-22 18:01 ` [PATCH 02/14] Add stack-skip frame count for rawtp provider eugene.loh
2025-06-13 14:35 ` Nick Alcock
2025-05-22 18:01 ` [PATCH 03/14] Test: remove unnecessary "unstable" tag eugene.loh
2025-06-13 14:35 ` [DTrace-devel] " Nick Alcock
2025-05-22 18:01 ` [PATCH 04/14] Test: caller and stackdepth tests for fbt provider eugene.loh
2025-06-13 14:40 ` [DTrace-devel] " Nick Alcock
2025-06-16 19:43 ` Eugene Loh
2025-06-25 4:14 ` Kris Van Hees
2025-05-22 18:01 ` [PATCH 05/14] Test: caller and stackdepth tests for dtrace provider eugene.loh
2025-06-13 14:42 ` Nick Alcock
2025-05-22 18:01 ` [PATCH 06/14] Test: caller and stackdepth tests for rawtp provider eugene.loh
2025-06-13 14:45 ` Nick Alcock
2025-05-22 18:01 ` [PATCH 07/14] Test: caller and stackdepth tests for cpc provider eugene.loh
2025-06-13 14:48 ` [DTrace-devel] " Nick Alcock
2025-05-22 18:01 ` [PATCH 08/14] Test: caller and stackdepth tests for ip provider eugene.loh
2025-06-13 14:51 ` [DTrace-devel] " Nick Alcock
2025-06-17 3:38 ` Eugene Loh
2025-06-25 4:15 ` Kris Van Hees
2025-05-22 18:01 ` [PATCH 09/14] Test: caller and stackdepth tests for profile provider eugene.loh
2025-06-13 14:52 ` [DTrace-devel] " Nick Alcock
2025-05-22 18:01 ` [PATCH 10/14] Test: caller and stackdepth tests for sched provider eugene.loh
2025-06-13 14:52 ` Nick Alcock
2025-05-22 18:01 ` [PATCH 11/14] Test: caller and stackdepth tests for proc provider eugene.loh
2025-06-13 14:53 ` Nick Alcock
2025-06-15 17:50 ` Eugene Loh
2025-06-19 12:52 ` Nick Alcock
2025-06-25 4:18 ` Kris Van Hees
2025-05-22 18:01 ` [PATCH 12/14] Test: caller and stackdepth tests for rawfbt provider eugene.loh
2025-06-13 14:54 ` [DTrace-devel] " Nick Alcock
2025-06-17 23:17 ` Eugene Loh
2025-05-22 18:01 ` [PATCH 13/14] Test: caller and stackdepth tests for io provider eugene.loh
2025-06-13 14:56 ` Nick Alcock [this message]
2025-05-22 18:01 ` [PATCH 14/14] Test: caller and stackdepth tests for lockstat provider eugene.loh
2025-06-13 14:57 ` Nick Alcock
2025-06-13 14:33 ` [PATCH 01/14] Fix stack-skip counts for caller and stackdepth Nick Alcock
2025-06-16 19:21 ` Eugene Loh
2025-06-19 13:03 ` Nick Alcock
2025-06-19 16:20 ` Kris Van Hees
2025-06-19 16:32 ` Kris Van Hees
2025-06-23 14:04 ` Nick Alcock
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=87a56bbsgr.fsf@esperi.org.uk \
--to=nick.alcock@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.