[Bug 269576] dtrace: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry): invalid address (0x0) in action #2

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 15 Feb 2023 22:14:43 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269576

            Bug ID: 269576
           Summary: dtrace: error on enabled probe ID 1 (ID 51902:
                    vfs:vop:vop_read:entry): invalid address (0x0) in
                    action #2
           Product: Base System
           Version: 13.0-RELEASE
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: 0mp@FreeBSD.org

Hi,

I'm executing the following DTrace command on FreeBSD 13.1-RELEASE arm64:

    dtrace -s ./script -c ./workload

The ./script is:

    vfs::vop_read:entry { @[ustack()] = count() }

The ./workload is:


    #! /bin/sh -
    set -eu
    exec dd if=/dev/zero of=/dev/null bs=1 count="$((10 * 1000 * 1000))"

I'm getting the following output (including error messages):

    dtrace: script './script' matched 1 probe
    dtrace: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry):
invalid address (0x0) in action #2
    dtrace: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry):
invalid address (0x0) in action #2
    dtrace: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry):
invalid address (0x0) in action #2
    dtrace: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry):
invalid address (0x0) in action #2
    10000000+0 records in
    10000000+0 records out
    10000000 bytes transferred in 3.003361 secs (3329603 bytes/sec)
    dtrace: pid 1830 has exited

Any idea what is causing those error messages? 

Oddly enough, if I specify the workload command directly on the command line,
i.e.,

    dtrace -s ./script -c "dd if=/dev/zero of=/dev/null bs=1 count=$((10 * 1000
* 1000))"

the error messages are not showing up.

-- 
You are receiving this mail because:
You are the assignee for the bug.