{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.mxEHvi1C/b1/systemtap_5.1-5_amd64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.mxEHvi1C/b2/systemtap_5.1-5_amd64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,11 +1,11 @@\n \n 7fea7b3128732f41cc8bba686d6b4f8b 8620 devel optional systemtap-client_5.1-5_amd64.deb\n fc384402acaae2e3995a1b23d9d7a0d2 640188 devel optional systemtap-common_5.1-5_amd64.deb\n 73ea489657e059948a08140dabf0941c 22024648 debug optional systemtap-dbgsym_5.1-5_amd64.deb\n- f2af0d1e8113d2ebb2296cd415f7935b 2583864 doc optional systemtap-doc_5.1-5_amd64.deb\n+ 4fd454d523a2c65b8d93b57aa297c309 2584180 doc optional systemtap-doc_5.1-5_amd64.deb\n d9f7a19d618fb649a03ec298bc379319 1270504 debug optional systemtap-runtime-dbgsym_5.1-5_amd64.deb\n d5c05014f6889c09eda32336ee91a7bb 148592 devel optional systemtap-runtime_5.1-5_amd64.deb\n 1cb2231c05fc4d247e6639bb546fb96f 18960 devel optional systemtap-sdt-dev_5.1-5_amd64.deb\n dbcd3935d839fb284ed28ff34b8f8f87 2092540 debug optional systemtap-server-dbgsym_5.1-5_amd64.deb\n 60f8b00f6897cb27529677907bbe8884 163392 devel optional systemtap-server_5.1-5_amd64.deb\n 7cb98f00844b7f7208c9351d4cf7905f 1530208 devel optional systemtap_5.1-5_amd64.deb\n"}, {"source1": "systemtap-doc_5.1-5_amd64.deb", "source2": "systemtap-doc_5.1-5_amd64.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2025-07-01 13:52:26.000000 debian-binary\n--rw-r--r-- 0 0 0 54236 2025-07-01 13:52:26.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2529436 2025-07-01 13:52:26.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 54260 2025-07-01 13:52:26.000000 control.tar.xz\n+-rw-r--r-- 0 0 0 2529728 2025-07-01 13:52:26.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -217,15 +217,15 @@\n -rw-r--r-- 0 root (0) root (0) 2297 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-asmlinkage.html\n -rw-r--r-- 0 root (0) root (0) 2987 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-assert.html\n -rw-r--r-- 0 root (0) root (0) 2705 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-atomic-long-read.html\n -rw-r--r-- 0 root (0) root (0) 2579 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-atomic-read.html\n -rw-r--r-- 0 root (0) root (0) 2408 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-backtrace.html\n -rw-r--r-- 0 root (0) root (0) 2937 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-bytes-to-string.html\n -rw-r--r-- 0 root (0) root (0) 2205 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller-addr.html\n--rw-r--r-- 0 root (0) root (0) 2457 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller.html\n+-rw-r--r-- 0 root (0) root (0) 2523 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller.html\n -rw-r--r-- 0 root (0) root (0) 2638 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-callers.html\n -rw-r--r-- 0 root (0) root (0) 2615 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-arg.html\n -rw-r--r-- 0 root (0) root (0) 3155 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-args.html\n -rw-r--r-- 0 root (0) root (0) 2328 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-str.html\n -rw-r--r-- 0 root (0) root (0) 2542 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-commit.html\n -rw-r--r-- 0 root (0) root (0) 2574 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cpu-clock-ms.html\n -rw-r--r-- 0 root (0) root (0) 2614 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cpu-clock-ns.html\n@@ -334,15 +334,15 @@\n -rw-r--r-- 0 root (0) root (0) 2673 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-isinstr.html\n -rw-r--r-- 0 root (0) root (0) 2421 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-jiffies.html\n -rw-r--r-- 0 root (0) root (0) 3229 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array-numeric-metric.html\n -rw-r--r-- 0 root (0) root (0) 3095 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array-string-metric.html\n -rw-r--r-- 0 root (0) root (0) 2837 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array.html\n -rw-r--r-- 0 root (0) root (0) 2978 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-numeric-metric.html\n -rw-r--r-- 0 root (0) root (0) 2749 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-string-metric.html\n--rw-r--r-- 0 root (0) root (0) 2975 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-data.html\n+-rw-r--r-- 0 root (0) root (0) 2909 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-data.html\n -rw-r--r-- 0 root (0) root (0) 3362 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-array-numeric-value.html\n -rw-r--r-- 0 root (0) root (0) 3374 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-array-string-value.html\n -rw-r--r-- 0 root (0) root (0) 2493 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-data-end.html\n -rw-r--r-- 0 root (0) root (0) 2471 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-data-start.html\n -rw-r--r-- 0 root (0) root (0) 2918 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-numeric-value.html\n -rw-r--r-- 0 root (0) root (0) 2847 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-string-value.html\n -rw-r--r-- 0 root (0) root (0) 2783 2025-07-01 13:52:26.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-set-prefix.html\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-caller.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-caller.html", "unified_diff": "@@ -3,9 +3,9 @@\n

Synopsis

\n     caller:string()\n

Arguments

\n None\n

Description

\n This function returns the address and name of the \n calling function. This is equivalent to calling:\n- sprintf(\"s 0xx\", symname(caller_addr), caller_addr)\n+ sprintf(“s 0xx”, symname(caller_addr), caller_addr)\n

Prev Up Next
function::backtrace Home function::caller_addr
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-end.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-end.html", "unified_diff": "@@ -1,41 +1,41 @@\n probe::ioblock.end
probe::ioblock.end
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock.end — \n Fires whenever a block I/O transfer is complete.\n-

Synopsis

ioblock.end

Values

name

\n- name of the probe point\n-

vcnt

\n- bio vector count which represents number of array element (page, offset, length) which makes up this I/O request\n-

phys_segments

\n- number of segments in this bio after physical address coalescing is performed.\n-

bytes_done

\n- number of bytes transferred\n-

hw_segments

\n- number of segments after physical and DMA remapping hardware coalescing is performed\n-

rw

\n- binary trace for read/write request\n+

Synopsis

ioblock.end

Values

devname

\n+ block device name\n

size

\n total size in bytes\n

opf

\n operations and flags\n

idx

\n offset into the bio vector array\n-

sector

\n- beginning sector for the entire bio\n-

error

\n- 0 on success\n+

phys_segments

\n+ number of segments in this bio after physical address coalescing is performed.\n

ino

\n i-node number of the mapped file\n

flags

\n see below\n BIO_UPTODATE 0 ok after I/O completion\n BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block\n BIO_EOF 2 out-out-bounds error\n BIO_SEG_VALID 3 nr_hw_seg valid\n BIO_CLONED 4 doesn't own data\n BIO_BOUNCED 5 bio is a bounce bio\n BIO_USER_MAPPED 6 contains user pages\n BIO_EOPNOTSUPP 7 not supported\n-

devname

\n- block device name\n+

sector

\n+ beginning sector for the entire bio\n+

rw

\n+ binary trace for read/write request\n+

name

\n+ name of the probe point\n+

hw_segments

\n+ number of segments after physical and DMA remapping hardware coalescing is performed\n+

vcnt

\n+ bio vector count which represents number of array element (page, offset, length) which makes up this I/O request\n+

bytes_done

\n+ number of bytes transferred\n+

error

\n+ 0 on success\n

Context

\n The process signals the transfer is done.\n

Prev Up Next
Chapter 9. IO Scheduler and block IO Tapset Home probe::ioblock.request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-request.html", "unified_diff": "@@ -1,43 +1,43 @@\n probe::ioblock.request
probe::ioblock.request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock.request — \n Fires whenever making a generic block I/O request.\n-

Synopsis

ioblock.request

Values

ino

\n- i-node number of the mapped file\n-

devname

\n+

Synopsis

ioblock.request

Values

devname

\n block device name\n-

bdev

\n- target block device\n+

size

\n+ total size in bytes\n+

opf

\n+ operations and flags\n+

idx

\n+ offset into the bio vector array\n+

ino

\n+ i-node number of the mapped file\n+

phys_segments

\n+ number of segments in this bio after physical address coalescing is performed\n

flags

\n see below\n BIO_UPTODATE 0 ok after I/O completion\n BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block\n BIO_EOF 2 out-out-bounds error\n BIO_SEG_VALID 3 nr_hw_seg valid \n BIO_CLONED 4 doesn't own data\n BIO_BOUNCED 5 bio is a bounce bio\n BIO_USER_MAPPED 6 contains user pages\n BIO_EOPNOTSUPP 7 not supported\n+

bdev

\n+ target block device\n

bdev_contains

\n points to the device object which contains the partition (when bio structure represents a partition)\n-

size

\n- total size in bytes\n-

idx

\n- offset into the bio vector array\n-

opf

\n- operations and flags\n

sector

\n beginning sector for the entire bio\n-

hw_segments

\n- number of segments after physical and DMA remapping hardware coalescing is performed\n-

rw

\n- binary trace for read/write request\n

name

\n name of the probe point\n+

rw

\n+ binary trace for read/write request\n+

hw_segments

\n+ number of segments after physical and DMA remapping hardware coalescing is performed\n

p_start_sect

\n points to the start sector of the partition structure of the device\n-

phys_segments

\n- number of segments in this bio after physical address coalescing is performed\n

vcnt

\n bio vector count which represents number of array element (page, offset, length) which make up this I/O request\n

Context

\n The process makes block I/O request\n

Prev Up Next
probe::ioblock.end Home probe::ioblock_trace.bounce
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-bounce.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-bounce.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,44 +1,44 @@\n probe::ioblock_trace.bounce
probe::ioblock_trace.bounce
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.bounce — \n Fires whenever a buffer bounce is needed for at least one page of a block IO request.\n

Synopsis

ioblock_trace.bounce

Values

bytes_done

\n number of bytes transferred\n

vcnt

\n bio vector count which represents number of array element (page, offset, length) which makes up this I/O request\n-

p_start_sect

\n- points to the start sector of the partition structure of the device\n

name

\n name of the probe point\n-

rw

\n- binary trace for read/write request\n-

sector

\n- beginning sector for the entire bio\n-

size

\n- total size in bytes\n-

opf

\n- operations and flags\n-

idx

\n- offset into the bio vector array\n- phys_segments - number of segments in this bio after physical address coalescing is performed.\n

q

\n request queue on which this bio was queued.\n+

rw

\n+ binary trace for read/write request\n+

p_start_sect

\n+ points to the start sector of the partition structure of the device\n+

ino

\n+ i-node number of the mapped file\n

bdev_contains

\n points to the device object which contains the partition (when bio structure represents a partition)\n

bdev

\n target block device\n+

sector

\n+ beginning sector for the entire bio\n

flags

\n see below\n BIO_UPTODATE 0 ok after I/O completion\n BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block\n BIO_EOF 2 out-out-bounds error\n BIO_SEG_VALID 3 nr_hw_seg valid\n BIO_CLONED 4 doesn't own data\n BIO_BOUNCED 5 bio is a bounce bio\n BIO_USER_MAPPED 6 contains user pages\n BIO_EOPNOTSUPP 7 not supported\n

devname

\n device for which a buffer bounce was needed.\n-

ino

\n- i-node number of the mapped file\n+

size

\n+ total size in bytes\n+

idx

\n+ offset into the bio vector array\n+ phys_segments - number of segments in this bio after physical address coalescing is performed.\n+

opf

\n+ operations and flags\n

Context

\n The process creating a block IO request.\n

Prev Up Next
probe::ioblock.request Home probe::ioblock_trace.end
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-end.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-end.html", "unified_diff": "@@ -1,44 +1,44 @@\n probe::ioblock_trace.end
probe::ioblock_trace.end
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.end — \n Fires whenever a block I/O transfer is complete.\n-

Synopsis

ioblock_trace.end

Values

name

\n- name of the probe point\n-

p_start_sect

\n- points to the start sector of the partition structure of the device\n+

Synopsis

ioblock_trace.end

Values

bytes_done

\n+ number of bytes transferred\n

vcnt

\n bio vector count which represents number of array element (page, offset, length) which makes up this I/O request\n-

bytes_done

\n- number of bytes transferred\n+

p_start_sect

\n+ points to the start sector of the partition structure of the device\n

rw

\n binary trace for read/write request\n-

idx

\n- offset into the bio vector array\n- phys_segments - number of segments in this bio after physical address coalescing is performed.\n-

size

\n- total size in bytes\n-

opf

\n- operations and flags\n-

bdev_contains

\n- points to the device object which contains the partition (when bio structure represents a partition)\n+

name

\n+ name of the probe point\n

q

\n request queue on which this bio was queued.\n

sector

\n beginning sector for the entire bio\n-

ino

\n- i-node number of the mapped file\n+

bdev

\n+ target block device\n+

bdev_contains

\n+ points to the device object which contains the partition (when bio structure represents a partition)\n

flags

\n see below\n BIO_UPTODATE 0 ok after I/O completion\n BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block\n BIO_EOF 2 out-out-bounds error\n BIO_SEG_VALID 3 nr_hw_seg valid\n BIO_CLONED 4 doesn't own data\n BIO_BOUNCED 5 bio is a bounce bio\n BIO_USER_MAPPED 6 contains user pages\n BIO_EOPNOTSUPP 7 not supported\n-

bdev

\n- target block device\n+

ino

\n+ i-node number of the mapped file\n+

idx

\n+ offset into the bio vector array\n+ phys_segments - number of segments in this bio after physical address coalescing is performed.\n+

opf

\n+ operations and flags\n

devname

\n block device name\n+

size

\n+ total size in bytes\n

Context

\n The process signals the transfer is done.\n

Prev Up Next
probe::ioblock_trace.bounce Home probe::ioblock_trace.request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-request.html", "unified_diff": "@@ -1,44 +1,44 @@\n probe::ioblock_trace.request
probe::ioblock_trace.request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.request — \n Fires just as a generic block I/O request is created for a bio.\n-

Synopsis

ioblock_trace.request

Values

vcnt

\n- bio vector count which represents number of array element (page, offset, length) which make up this I/O request\n-

bytes_done

\n+

Synopsis

ioblock_trace.request

Values

bytes_done

\n number of bytes transferred\n+

vcnt

\n+ bio vector count which represents number of array element (page, offset, length) which make up this I/O request\n

p_start_sect

\n points to the start sector of the partition structure of the device\n-

name

\n- name of the probe point\n

rw

\n binary trace for read/write request\n+

name

\n+ name of the probe point\n+

q

\n+ request queue on which this bio was queued.\n

sector

\n beginning sector for the entire bio\n-

idx

\n- offset into the bio vector array\n- phys_segments - number of segments in this bio after physical address coalescing is performed.\n-

size

\n- total size in bytes\n-

opf

\n- operations and flags\n+

bdev

\n+ target block device\n

bdev_contains

\n points to the device object which contains the partition (when bio structure represents a partition)\n-

q

\n- request queue on which this bio was queued.\n

flags

\n see below\n BIO_UPTODATE 0 ok after I/O completion\n BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block\n BIO_EOF 2 out-out-bounds error\n BIO_SEG_VALID 3 nr_hw_seg valid\n BIO_CLONED 4 doesn't own data\n BIO_BOUNCED 5 bio is a bounce bio\n BIO_USER_MAPPED 6 contains user pages\n BIO_EOPNOTSUPP 7 not supported\n-

bdev

\n- target block device\n-

devname

\n- block device name\n

ino

\n i-node number of the mapped file\n+

idx

\n+ offset into the bio vector array\n+ phys_segments - number of segments in this bio after physical address coalescing is performed.\n+

opf

\n+ operations and flags\n+

size

\n+ total size in bytes\n+

devname

\n+ block device name\n

Context

\n The process makes block I/O request\n

Prev Up Next
probe::ioblock_trace.end Home probe::ioscheduler.elv_add_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-kp.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-kp.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::ioscheduler.elv_add_request.kp
probe::ioscheduler.elv_add_request.kp
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request.kp — \n kprobe based probe to indicate that a request was added to the request queue\n-

Synopsis

ioscheduler.elv_add_request.kp

Values

rq

\n- Address of the request\n+

Synopsis

ioscheduler.elv_add_request.kp

Values

disk_major

\n+ Disk major number of the request\n

q

\n pointer to request queue\n+

rq_flags

\n+ Request flags\n

elevator_name

\n The type of I/O elevator currently enabled\n

name

\n Name of the probe point\n-

rq_flags

\n- Request flags\n-

disk_major

\n- Disk major number of the request\n

disk_minor

\n Disk minor number of the request\n+

rq

\n+ Address of the request\n

Prev Up Next
probe::ioscheduler.elv_add_request Home probe::ioscheduler.elv_add_request.tp
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-tp.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-tp.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,17 +1,17 @@\n probe::ioscheduler.elv_add_request.tp
probe::ioscheduler.elv_add_request.tp
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request.tp — \n tracepoint based probe to indicate a request is added to the request queue.\n

Synopsis

ioscheduler.elv_add_request.tp

Values

rq_flags

\n Request flags.\n

disk_major

\n Disk major no of request.\n-

disk_minor

\n- Disk minor number of request.\n-

rq

\n- Address of request.\n

q

\n Pointer to request queue.\n-

elevator_name

\n- The type of I/O elevator currently enabled.\n+

rq

\n+ Address of request.\n+

disk_minor

\n+ Disk minor number of request.\n

name

\n Name of the probe point\n+

elevator_name

\n+ The type of I/O elevator currently enabled.\n

Prev Up Next
probe::ioscheduler.elv_add_request.kp Home probe::ioscheduler.elv_completed_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::ioscheduler.elv_add_request
probe::ioscheduler.elv_add_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request — \n probe to indicate request is added to the request queue.\n-

Synopsis

ioscheduler.elv_add_request

Values

elevator_name

\n- The type of I/O elevator currently enabled.\n-

rq

\n- Address of request.\n-

q

\n+

Synopsis

ioscheduler.elv_add_request

Values

q

\n Pointer to request queue.\n

disk_major

\n Disk major no of request.\n-

disk_minor

\n- Disk minor number of request.\n

rq_flags

\n Request flags.\n+

rq

\n+ Address of request.\n+

elevator_name

\n+ The type of I/O elevator currently enabled.\n+

disk_minor

\n+ Disk minor number of request.\n

Prev Up Next
probe::ioblock_trace.request Home probe::ioscheduler.elv_add_request.kp
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-completed-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-completed-request.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::ioscheduler.elv_completed_request
probe::ioscheduler.elv_completed_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_completed_request — \n Fires when a request is completed\n-

Synopsis

ioscheduler.elv_completed_request

Values

disk_minor

\n- Disk minor number of the request\n+

Synopsis

ioscheduler.elv_completed_request

Values

rq_flags

\n+ Request flags\n

disk_major

\n Disk major number of the request\n

rq

\n Address of the request\n-

rq_flags

\n- Request flags\n-

name

\n- Name of the probe point\n

elevator_name

\n The type of I/O elevator currently enabled\n+

disk_minor

\n+ Disk minor number of the request\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::ioscheduler.elv_add_request.tp Home probe::ioscheduler.elv_next_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-next-request-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-next-request-return.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::ioscheduler.elv_next_request.return
probe::ioscheduler.elv_next_request.return
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_next_request.return — \n Fires when a request retrieval issues a return signal\n-

Synopsis

ioscheduler.elv_next_request.return

Values

name

\n- Name of the probe point\n-

disk_major

\n- Disk major number of the request\n-

rq

\n+

Synopsis

ioscheduler.elv_next_request.return

Values

rq

\n Address of the request\n-

disk_minor

\n- Disk minor number of the request\n

rq_flags

\n Request flags\n+

disk_minor

\n+ Disk minor number of the request\n+

name

\n+ Name of the probe point\n+

disk_major

\n+ Disk major number of the request\n

Prev Up Next
probe::ioscheduler.elv_next_request Home probe::ioscheduler_trace.elv_abort_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-next-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-next-request.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::ioscheduler.elv_next_request
probe::ioscheduler.elv_next_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_next_request — \n Fires when a request is retrieved from the request queue\n-

Synopsis

ioscheduler.elv_next_request

Values

elevator_name

\n- The type of I/O elevator currently enabled\n-

name

\n+

Synopsis

ioscheduler.elv_next_request

Values

name

\n Name of the probe point\n+

elevator_name

\n+ The type of I/O elevator currently enabled\n

Prev Up Next
probe::ioscheduler.elv_completed_request Home probe::ioscheduler.elv_next_request.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-abort-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-abort-request.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::ioscheduler_trace.elv_abort_request
probe::ioscheduler_trace.elv_abort_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_abort_request — \n Fires when a request is aborted.\n-

Synopsis

ioscheduler_trace.elv_abort_request

Values

rq_flags

\n- Request flags.\n-

disk_major

\n+

Synopsis

ioscheduler_trace.elv_abort_request

Values

disk_major

\n Disk major no of request.\n+

rq_flags

\n+ Request flags.\n+

rq

\n+ Address of request.\n+

name

\n+ Name of the probe point\n

disk_minor

\n Disk minor number of request.\n

elevator_name

\n The type of I/O elevator currently enabled.\n-

name

\n- Name of the probe point\n-

rq

\n- Address of request.\n

Prev Up Next
probe::ioscheduler.elv_next_request.return Home probe::ioscheduler_trace.elv_completed_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-completed-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-completed-request.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::ioscheduler_trace.elv_completed_request
probe::ioscheduler_trace.elv_completed_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_completed_request — \n Fires when a request is\n-

Synopsis

ioscheduler_trace.elv_completed_request

Values

rq

\n+

Synopsis

ioscheduler_trace.elv_completed_request

Values

disk_major

\n+ Disk major no of request.\n+

rq_flags

\n+ Request flags.\n+

rq

\n Address of request.\n

elevator_name

\n The type of I/O elevator currently enabled.\n-

name

\n- Name of the probe point\n-

rq_flags

\n- Request flags.\n-

disk_major

\n- Disk major no of request.\n

disk_minor

\n Disk minor number of request.\n+

name

\n+ Name of the probe point\n

Description

\n completed.\n

Prev Up Next
probe::ioscheduler_trace.elv_abort_request Home probe::ioscheduler_trace.elv_issue_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-issue-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-issue-request.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::ioscheduler_trace.elv_issue_request
probe::ioscheduler_trace.elv_issue_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_issue_request — \n Fires when a request is\n-

Synopsis

ioscheduler_trace.elv_issue_request

Values

rq_flags

\n+

Synopsis

ioscheduler_trace.elv_issue_request

Values

disk_major

\n+ Disk major no of request.\n+

rq_flags

\n Request flags.\n+

rq

\n+ Address of request.\n+

elevator_name

\n+ The type of I/O elevator currently enabled.\n

disk_minor

\n Disk minor number of request.\n-

disk_major

\n- Disk major no of request.\n

name

\n Name of the probe point\n-

elevator_name

\n- The type of I/O elevator currently enabled.\n-

rq

\n- Address of request.\n

Description

\n scheduled.\n

Prev Up Next
probe::ioscheduler_trace.elv_completed_request Home probe::ioscheduler_trace.elv_requeue_request
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-requeue-request.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-requeue-request.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::ioscheduler_trace.elv_requeue_request
probe::ioscheduler_trace.elv_requeue_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_requeue_request — \n Fires when a request is\n-

Synopsis

ioscheduler_trace.elv_requeue_request

Values

disk_major

\n- Disk major no of request.\n-

disk_minor

\n- Disk minor number of request.\n-

rq_flags

\n- Request flags.\n+

Synopsis

ioscheduler_trace.elv_requeue_request

Values

rq

\n+ Address of request.\n

elevator_name

\n The type of I/O elevator currently enabled.\n

name

\n Name of the probe point\n-

rq

\n- Address of request.\n+

disk_minor

\n+ Disk minor number of request.\n+

rq_flags

\n+ Request flags.\n+

disk_major

\n+ Disk major no of request.\n

Description

\n put back on the queue, when the hadware cannot accept more requests.\n

Prev Up Next
probe::ioscheduler_trace.elv_issue_request Home probe::ioscheduler_trace.plug
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-unplug-io.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-unplug-io.html", "unified_diff": "@@ -1,10 +1,10 @@\n probe::ioscheduler_trace.unplug_io
probe::ioscheduler_trace.unplug_io
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.unplug_io — \n Fires when a request queue is unplugged;\n-

Synopsis

ioscheduler_trace.unplug_io

Values

name

\n- Name of the probe point\n-

rq_queue

\n+

Synopsis

ioscheduler_trace.unplug_io

Values

rq_queue

\n request queue\n+

name

\n+ Name of the probe point\n

Description

\n Either, when number of pending requests in the queue exceeds threshold\n or, upon expiration of timer that was activated when queue was plugged.\n

Prev Up Next
probe::ioscheduler_trace.plug Home probe::ioscheduler_trace.unplug_timer
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-ForwDatagrams.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-ForwDatagrams.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::ipmib.ForwDatagrams
probe::ipmib.ForwDatagrams
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.ForwDatagrams — \n Count forwarded packet\n-

Synopsis

ipmib.ForwDatagrams

Values

skb

\n- pointer to the struct sk_buff being acted on\n-

op

\n+

Synopsis

ipmib.ForwDatagrams

Values

op

\n value to be added to the counter (default value of 1)\n+

skb

\n+ pointer to the struct sk_buff being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n ipmib_filter_key. If the packet passes the filter is is\n counted in the global ForwDatagrams (equivalent to SNMP's MIB\n IPSTATS_MIB_OUTFORWDATAGRAMS)\n

Prev Up Next
function::tcpmib_remote_port Home probe::ipmib.FragFails
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-FragOKs.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-FragOKs.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::ipmib.FragOKs
probe::ipmib.FragOKs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.FragOKs — \n Count datagram fragmented successfully\n-

Synopsis

ipmib.FragOKs

Values

skb

\n- pointer to the struct sk_buff being acted on\n-

op

\n+

Synopsis

ipmib.FragOKs

Values

op

\n value to be added to the counter (default value of 1)\n+

skb

\n+ pointer to the struct sk_buff being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n ipmib_filter_key. If the packet passes the filter is is\n counted in the global FragOKs (equivalent to SNMP's MIB\n IPSTATS_MIB_FRAGOKS)\n

Prev Up Next
probe::ipmib.FragFails Home probe::ipmib.InAddrErrors
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InReceives.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InReceives.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::ipmib.InReceives
probe::ipmib.InReceives
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.InReceives — \n Count an arriving packet\n-

Synopsis

ipmib.InReceives

Values

op

\n- value to be added to the counter (default value of 1)\n-

skb

\n+

Synopsis

ipmib.InReceives

Values

skb

\n pointer to the struct sk_buff being acted on\n+

op

\n+ value to be added to the counter (default value of 1)\n

Description

\n The packet pointed to by skb is filtered by the function\n ipmib_filter_key. If the packet passes the filter is is\n counted in the global InReceives (equivalent to SNMP's MIB\n IPSTATS_MIB_INRECEIVES)\n

Prev Up Next
probe::ipmib.InNoRoutes Home probe::ipmib.InUnknownProtos
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InUnknownProtos.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InUnknownProtos.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::ipmib.InUnknownProtos
probe::ipmib.InUnknownProtos
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.InUnknownProtos — \n Count arriving packets with an unbound proto\n-

Synopsis

ipmib.InUnknownProtos

Values

op

\n- value to be added to the counter (default value of 1)\n-

skb

\n+

Synopsis

ipmib.InUnknownProtos

Values

skb

\n pointer to the struct sk_buff being acted on\n+

op

\n+ value to be added to the counter (default value of 1)\n

Description

\n The packet pointed to by skb is filtered by the function\n ipmib_filter_key. If the packet passes the filter is is\n counted in the global InUnknownProtos (equivalent to SNMP's MIB\n IPSTATS_MIB_INUNKNOWNPROTOS)\n

Prev Up Next
probe::ipmib.InReceives Home probe::ipmib.OutRequests
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-OutRequests.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-ipmib-OutRequests.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::ipmib.OutRequests
probe::ipmib.OutRequests
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.OutRequests — \n Count a request to send a packet\n-

Synopsis

ipmib.OutRequests

Values

op

\n- value to be added to the counter (default value of 1)\n-

skb

\n+

Synopsis

ipmib.OutRequests

Values

skb

\n pointer to the struct sk_buff being acted on\n+

op

\n+ value to be added to the counter (default value of 1)\n

Description

\n The packet pointed to by skb is filtered by the function\n ipmib_filter_key. If the packet passes the filter is is\n counted in the global OutRequests (equivalent to SNMP's MIB\n IPSTATS_MIB_OUTREQUESTS)\n

Prev Up Next
probe::ipmib.InUnknownProtos Home probe::ipmib.ReasmReqds
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-entry.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-entry.html", "unified_diff": "@@ -1,27 +1,27 @@\n probe::irq_handler.entry
probe::irq_handler.entry
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::irq_handler.entry — \n Execution of interrupt handler starting\n-

Synopsis

irq_handler.entry

Values

handler

\n- interrupt handler function\n-

dev_name

\n- name of device\n-

action

\n- struct irqaction* for this interrupt num\n-

thread_fn

\n- interrupt handler function for threaded interrupts\n+

Synopsis

irq_handler.entry

Values

flags_str

\n+ symbolic string representation of IRQ flags\n+

flags

\n+ Flags for IRQ handler\n+

next_irqaction

\n+ pointer to next irqaction for shared interrupts\n

dir

\n pointer to the proc/irq/NN/name entry\n+

thread_flags

\n+ Flags related to thread\n

irq

\n irq number\n-

thread

\n- thread pointer for threaded interrupts\n-

flags

\n- Flags for IRQ handler\n+

thread_fn

\n+ interrupt handler function for threaded interrupts\n

dev_id

\n Cookie to identify device\n-

flags_str

\n- symbolic string representation of IRQ flags\n-

thread_flags

\n- Flags related to thread\n-

next_irqaction

\n- pointer to next irqaction for shared interrupts\n+

action

\n+ struct irqaction* for this interrupt num\n+

dev_name

\n+ name of device\n+

thread

\n+ thread pointer for threaded interrupts\n+

handler

\n+ interrupt handler function\n

Prev Up Next
Chapter 12. Interrupt Request (IRQ) Tapset Home probe::irq_handler.exit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-exit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-exit.html", "unified_diff": "@@ -1,29 +1,29 @@\n probe::irq_handler.exit
probe::irq_handler.exit
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::irq_handler.exit — \n Execution of interrupt handler completed\n-

Synopsis

irq_handler.exit

Values

dev_id

\n+

Synopsis

irq_handler.exit

Values

thread_fn

\n+ interrupt handler function for threaded interrupts\n+

dev_id

\n Cookie to identify device\n-

flags

\n- flags for IRQ handler\n+

dev_name

\n+ name of device\n

thread

\n thread pointer for threaded interrupts\n-

next_irqaction

\n- pointer to next irqaction for shared interrupts\n-

flags_str

\n- symbolic string representation of IRQ flags\n-

thread_flags

\n- Flags related to thread\n-

thread_fn

\n- interrupt handler function for threaded interrupts\n

action

\n struct irqaction*\n-

dev_name

\n- name of device\n

handler

\n interrupt handler function that was executed\n

ret

\n return value of the handler\n-

irq

\n- interrupt number\n+

flags_str

\n+ symbolic string representation of IRQ flags\n+

flags

\n+ flags for IRQ handler\n+

next_irqaction

\n+ pointer to next irqaction for shared interrupts\n

dir

\n pointer to the proc/irq/NN/name entry\n+

thread_flags

\n+ Flags related to thread\n+

irq

\n+ interrupt number\n

Prev Up Next
probe::irq_handler.entry Home probe::softirq.entry
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-json-data.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-json-data.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::json_data
probe::json_data
Prev Chapter 33. JSON Tapset Next

Name

probe::json_data — \n Fires whenever JSON data is wanted by a reader.\n

Synopsis

json_data

Values

\n None\n

Context

\n This probe fires when the JSON data is about to be read. This\n probe must gather up data and then call the following macros to\n- output the data in JSON format. First, json_output_data_start()\n+ output the data in JSON format. First, @json_output_data_start\n must be called. That call is followed by one or more of the\n following (one call for each data item):\n- json_output_string_value(), json_output_numeric_value(),\n- json_output_array_string_value(), and\n- json_output_array_numeric_value(). Finally json_output_data_end()\n+ @json_output_string_value, @json_output_numeric_value,\n+ @json_output_array_string_value, and\n+ @json_output_array_numeric_value. Finally @json_output_data_end\n must be called. \n

Prev Up Next
macro::json_output_string_value Home Chapter 34. Output file switching Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec-complete.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec-complete.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::kprocess.exec_complete
probe::kprocess.exec_complete
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.exec_complete — \n Return from exec to a new program\n-

Synopsis

kprocess.exec_complete

Values

retstr

\n+

Synopsis

kprocess.exec_complete

Values

errno

\n+ The error number resulting from the exec\n+

retstr

\n A string representation of errno (SystemTap v2.5+)\n

success

\n A boolean indicating whether the exec was successful\n-

errno

\n- The error number resulting from the exec\n

name

\n Name of the system call (“execve”) (SystemTap v2.5+)\n

Context

\n On success, the context of the new executable.\n On failure, remains in the context of the caller.\n

Description

\n Fires at the completion of an exec call. Aliased to the\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec.html", "unified_diff": "@@ -1,16 +1,16 @@\n probe::kprocess.exec

probe::kprocess.exec
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.exec — \n Attempt to exec to a new program\n-

Synopsis

kprocess.exec

Values

argstr

\n- A string containing the filename followed by the\n- arguments to pass, excluding 0th arg (SystemTap v2.5+)\n-

name

\n+

Synopsis

kprocess.exec

Values

name

\n Name of the system call (“execve”) (SystemTap v2.5+)\n

filename

\n The path to the new executable\n+

argstr

\n+ A string containing the filename followed by the\n+ arguments to pass, excluding 0th arg (SystemTap v2.5+)\n

args

\n The arguments to pass to the new executable, including\n the 0th arg (SystemTap v2.5+)\n

Context

\n The caller of exec.\n

Description

\n Fires whenever a process attempts to exec to a new program. Aliased\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-release.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-kprocess-release.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::kprocess.release

probe::kprocess.release
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.release — \n Process released\n-

Synopsis

kprocess.release

Values

released_tid

\n- TID of the task being released\n+

Synopsis

kprocess.release

Values

pid

\n+ Same as released_pid for compatibility (deprecated)\n

task

\n A task handle to the process being released\n-

pid

\n- Same as released_pid for compatibility (deprecated)\n

released_pid

\n PID of the process being released\n+

released_tid

\n+ TID of the task being released\n

Context

\n The context of the parent, if it wanted notification of this process'\n termination, else the context of the process itself.\n

Description

\n Fires when a process is released from the kernel. This always follows a\n kprocess.exit, though it may be delayed somewhat if the process waits in a\n zombie state.\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-ListenOverflows.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-ListenOverflows.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::linuxmib.ListenOverflows

probe::linuxmib.ListenOverflows
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::linuxmib.ListenOverflows — \n Count of times a listen queue overflowed\n-

Synopsis

linuxmib.ListenOverflows

Values

sk

\n- Pointer to the struct sock being acted on\n-

op

\n+

Synopsis

linuxmib.ListenOverflows

Values

op

\n Value to be added to the counter (default value of 1)\n+

sk

\n+ Pointer to the struct sock being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n linuxmib_filter_key. If the packet passes the filter is is\n counted in the global ListenOverflows (equivalent to SNMP's MIB\n LINUX_MIB_LISTENOVERFLOWS)\n

Prev Up Next
probe::linuxmib.ListenDrops Home probe::linuxmib.TCPMemoryPressures
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-TCPMemoryPressures.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-TCPMemoryPressures.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::linuxmib.TCPMemoryPressures
probe::linuxmib.TCPMemoryPressures
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::linuxmib.TCPMemoryPressures — \n Count of times memory pressure was used\n-

Synopsis

linuxmib.TCPMemoryPressures

Values

sk

\n- Pointer to the struct sock being acted on\n-

op

\n+

Synopsis

linuxmib.TCPMemoryPressures

Values

op

\n Value to be added to the counter (default value of 1)\n+

sk

\n+ Pointer to the struct sock being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n linuxmib_filter_key. If the packet passes the filter is is\n counted in the global TCPMemoryPressures (equivalent to SNMP's MIB\n LINUX_MIB_TCPMEMORYPRESSURES)\n

Prev Up Next
probe::linuxmib.ListenOverflows Home probe::tcpmib.ActiveOpens
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-mac.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-mac.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::netdev.change_mac
probe::netdev.change_mac
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.change_mac — \n Called when the netdev_name has the MAC changed\n-

Synopsis

netdev.change_mac

Values

dev_name

\n+

Synopsis

netdev.change_mac

Values

mac_len

\n+ The MAC length\n+

dev_name

\n The device that will have the MAC changed\n

old_mac

\n The current MAC address\n-

mac_len

\n- The MAC length\n

new_mac

\n The new MAC address\n

Prev Up Next
function::ntohs Home probe::netdev.change_mtu
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-mtu.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-mtu.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::netdev.change_mtu
probe::netdev.change_mtu
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.change_mtu — \n Called when the netdev MTU is changed\n-

Synopsis

netdev.change_mtu

Values

dev_name

\n- The device that will have the MTU changed\n+

Synopsis

netdev.change_mtu

Values

new_mtu

\n+ The new MTU\n

old_mtu

\n The current MTU\n-

new_mtu

\n- The new MTU\n+

dev_name

\n+ The device that will have the MTU changed\n

Prev Up Next
probe::netdev.change_mac Home probe::netdev.change_rx_flag
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-rx-flag.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-rx-flag.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::netdev.change_rx_flag
probe::netdev.change_rx_flag
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.change_rx_flag — \n Called when the device RX flag will be changed\n-

Synopsis

netdev.change_rx_flag

Values

dev_name

\n- The device that will be changed\n-

flags

\n+

Synopsis

netdev.change_rx_flag

Values

flags

\n The new flags\n+

dev_name

\n+ The device that will be changed\n

Prev Up Next
probe::netdev.change_mtu Home probe::netdev.close
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-hard-transmit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-hard-transmit.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::netdev.hard_transmit
probe::netdev.hard_transmit
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.hard_transmit — \n Called when the devices is going to TX (hard)\n-

Synopsis

netdev.hard_transmit

Values

truesize

\n- The size of the data to be transmitted.\n-

length

\n+

Synopsis

netdev.hard_transmit

Values

length

\n The length of the transmit buffer.\n+

truesize

\n+ The size of the data to be transmitted.\n

protocol

\n The protocol used in the transmission\n

dev_name

\n The device scheduled to transmit\n

Prev Up Next
probe::netdev.get_stats Home probe::netdev.ioctl
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-receive.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-receive.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::netdev.receive
probe::netdev.receive
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.receive — \n Data received from network device.\n-

Synopsis

netdev.receive

Values

dev_name

\n- The name of the device. e.g: eth0, ath1.\n+

Synopsis

netdev.receive

Values

length

\n+ The length of the receiving buffer.\n

protocol

\n Protocol of received packet.\n-

length

\n- The length of the receiving buffer.\n+

dev_name

\n+ The name of the device. e.g: eth0, ath1.\n

Prev Up Next
probe::netdev.open Home probe::netdev.register
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-set-promiscuity.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-set-promiscuity.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::netdev.set_promiscuity
probe::netdev.set_promiscuity
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.set_promiscuity — \n Called when the device enters/leaves promiscuity\n-

Synopsis

netdev.set_promiscuity

Values

dev_name

\n- The device that is entering/leaving promiscuity mode\n-

enable

\n- If the device is entering promiscuity mode\n-

inc

\n+

Synopsis

netdev.set_promiscuity

Values

inc

\n Count the number of promiscuity openers\n+

dev_name

\n+ The device that is entering/leaving promiscuity mode\n

disable

\n If the device is leaving promiscuity mode\n+

enable

\n+ If the device is entering promiscuity mode\n

Prev Up Next
probe::netdev.rx Home probe::netdev.transmit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-transmit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netdev-transmit.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::netdev.transmit
probe::netdev.transmit
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.transmit — \n Network device transmitting buffer\n-

Synopsis

netdev.transmit

Values

length

\n- The length of the transmit buffer.\n-

dev_name

\n+

Synopsis

netdev.transmit

Values

dev_name

\n The name of the device. e.g: eth0, ath1.\n

protocol

\n The protocol of this packet(defined in include/linux/if_ether.h).\n

truesize

\n The size of the data to be transmitted.\n+

length

\n+ The length of the transmit buffer.\n

Prev Up Next
probe::netdev.set_promiscuity Home probe::netdev.unregister
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-forward.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-forward.html", "unified_diff": "@@ -1,53 +1,53 @@\n probe::netfilter.arp.forward
probe::netfilter.arp.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.forward — \n - Called for each ARP packet to be forwarded\n-

Synopsis

netfilter.arp.forward

Values

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

arphdr

\n- Address of ARP header\n-

ar_op

\n+

Synopsis

netfilter.arp.forward

Values

ar_op

\n ARP opcode (command)\n+

pf

\n+ Protocol family -- always “arp”\n

nf_stop

\n Constant used to signify a 'stop' verdict\n-

ar_hrd

\n- Format of hardware address\n+

ar_sha

\n+ Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n+

indev_name

\n+ Name of network device packet was received on (if known)\n

ar_pln

\n Length of protocol address\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ar_sip

\n- Ethernet+IP only (ar_pro==0x800): source IP address\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

ar_data

\n+ Address of ARP packet data region (after the header)\n+

ar_tha

\n+ Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

arphdr

\n+ Address of ARP header\n+

ar_hrd

\n+ Format of hardware address\n

ar_tip

\n Ethernet+IP only (ar_pro==0x800): target IP address\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

ar_pro

\n+ Format of protocol address\n

nf_repeat

\n Constant used to signify a 'repeat' verdict\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n

data_str

\n A string representing the packet buffer contents\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n

length

\n The length of the packet buffer contents, in bytes\n-

pf

\n- Protocol family -- always “arp”\n-

ar_tha

\n- Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n-

ar_pro

\n- Format of protocol address\n-

ar_data

\n- Address of ARP packet data region (after the header)\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n

ar_hln

\n Length of hardware address\n-

ar_sha

\n- Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n-

indev_name

\n- Name of network device packet was received on (if known)\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

ar_sip

\n+ Ethernet+IP only (ar_pro==0x800): source IP address\n

Prev Up Next
probe::netdev.unregister Home probe::netfilter.arp.in
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-in.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-in.html", "unified_diff": "@@ -1,53 +1,53 @@\n probe::netfilter.arp.in
probe::netfilter.arp.in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.in — \n - Called for each incoming ARP packet\n-

Synopsis

netfilter.arp.in

Values

ar_tip

\n- Ethernet+IP only (ar_pro==0x800): target IP address\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n+

Synopsis

netfilter.arp.in

Values

ar_op

\n+ ARP opcode (command)\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n+

pf

\n+ Protocol family -- always “arp”\n+

ar_sha

\n+ Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

ar_pln

\n+ Length of protocol address\n+

ar_data

\n+ Address of ARP packet data region (after the header)\n

indev

\n Address of net_device representing input device, 0 if unknown\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

data_str

\n- A string representing the packet buffer contents\n+

ar_tha

\n+ Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n

data_hex

\n A hexadecimal string representing the packet buffer contents\n

arphdr

\n Address of ARP header\n-

ar_sip

\n- Ethernet+IP only (ar_pro==0x800): source IP address\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n-

ar_op

\n- ARP opcode (command)\n+

ar_tip

\n+ Ethernet+IP only (ar_pro==0x800): target IP address\n

ar_hrd

\n Format of hardware address\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ar_pln

\n- Length of protocol address\n-

ar_data

\n- Address of ARP packet data region (after the header)\n-

ar_hln

\n- Length of hardware address\n-

indev_name

\n- Name of network device packet was received on (if known)\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

ar_pro

\n+ Format of protocol address\n

nf_drop

\n Constant used to signify a 'drop' verdict\n-

ar_sha

\n- Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

data_str

\n+ A string representing the packet buffer contents\n

length

\n The length of the packet buffer contents, in bytes\n-

ar_tha

\n- Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n-

pf

\n- Protocol family -- always “arp”\n-

ar_pro

\n- Format of protocol address\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

ar_hln

\n+ Length of hardware address\n+

ar_sip

\n+ Ethernet+IP only (ar_pro==0x800): source IP address\n

Prev Up Next
probe::netfilter.arp.forward Home probe::netfilter.arp.out
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-out.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-out.html", "unified_diff": "@@ -1,53 +1,53 @@\n probe::netfilter.arp.out
probe::netfilter.arp.out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.out — \n - Called for each outgoing ARP packet\n-

Synopsis

netfilter.arp.out

Values

ar_sha

\n- Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

ar_hln

\n- Length of hardware address\n-

ar_data

\n- Address of ARP packet data region (after the header)\n-

ar_pro

\n- Format of protocol address\n+

Synopsis

netfilter.arp.out

Values

arphdr

\n+ Address of ARP header\n+

ar_tip

\n+ Ethernet+IP only (ar_pro==0x800): target IP address\n+

ar_hrd

\n+ Format of hardware address\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n

length

\n The length of the packet buffer contents, in bytes\n-

ar_tha

\n- Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n-

pf

\n- Protocol family -- always “arp”\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n

data_str

\n A string representing the packet buffer contents\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n

nf_queue

\n Constant used to signify a 'queue' verdict\n-

ar_tip

\n- Ethernet+IP only (ar_pro==0x800): target IP address\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ar_pln

\n- Length of protocol address\n+

ar_hln

\n+ Length of hardware address\n+

ar_sip

\n+ Ethernet+IP only (ar_pro==0x800): source IP address\n+

ar_pro

\n+ Format of protocol address\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

ar_sha

\n+ Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address \n

ar_op

\n ARP opcode (command)\n+

pf

\n+ Protocol family -- always “arp”\n

nf_stop

\n Constant used to signify a 'stop' verdict\n-

ar_hrd

\n- Format of hardware address\n-

ar_sip

\n- Ethernet+IP only (ar_pro==0x800): source IP address\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

arphdr

\n- Address of ARP header\n+

ar_data

\n+ Address of ARP packet data region (after the header)\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

ar_tha

\n+ Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address\n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

ar_pln

\n+ Length of protocol address\n

Prev Up Next
probe::netfilter.arp.in Home probe::netfilter.bridge.forward
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-forward.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-forward.html", "unified_diff": "@@ -1,67 +1,67 @@\n probe::netfilter.bridge.forward
probe::netfilter.bridge.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.forward — \n Called on an incoming bridging packet destined for some other computer\n-

Synopsis

netfilter.bridge.forward

Values

br_poid

\n- Port identifier\n-

br_bid

\n- Identity of bridge\n-

llcproto_stp

\n- Constant used to signify Bridge Spanning Tree Protocol packet\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

br_flags

\n- BPDU flags\n+

Synopsis

netfilter.bridge.forward

Values

br_prid

\n+ Protocol identifier\n+

protocol

\n+ Packet protocol\n+

llcpdu

\n+ Address of LLC Protocol Data Unit\n+

pf

\n+ Protocol family -- always “bridge”\n

nf_stop

\n Constant used to signify a 'stop' verdict\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

br_type

\n- BPDU type\n+

br_htime

\n+ Hello time in 1/256 secs\n+

brhdr

\n+ Address of bridge header\n

indev

\n Address of net_device representing input device, 0 if unknown\n+

br_max

\n+ Max age in 1/256 secs\n+

br_flags

\n+ BPDU flags\n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

br_type

\n+ BPDU type\n+

br_bid

\n+ Identity of bridge\n+

br_mac

\n+ Bridge MAC address\n+

br_msg

\n+ Message age in 1/256 secs\n

outdev

\n Address of net_device representing output device, 0 if unknown\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

data_str

\n- A string representing the packet buffer contents\n+

br_fd

\n+ Forward delay in 1/256 secs\n+

llcproto_stp

\n+ Constant used to signify Bridge Spanning Tree Protocol packet\n+

br_poid

\n+ Port identifier\n

br_cost

\n Total cost from transmitting bridge to root\n-

br_msg

\n- Message age in 1/256 secs\n-

br_htime

\n- Hello time in 1/256 secs\n-

protocol

\n- Packet protocol\n-

br_mac

\n- Bridge MAC address\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n-

br_fd

\n- Forward delay in 1/256 secs\n-

llcpdu

\n- Address of LLC Protocol Data Unit\n-

br_prid

\n- Protocol identifier\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

data_str

\n+ A string representing the packet buffer contents\n

length

\n The length of the packet buffer contents, in bytes\n-

pf

\n- Protocol family -- always “bridge”\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n-

brhdr

\n- Address of bridge header\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

br_vid

\n- Protocol version identifier\n

br_rid

\n Identity of root bridge\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

br_vid

\n+ Protocol version identifier\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n

br_rmac

\n Root bridge MAC address\n-

br_max

\n- Max age in 1/256 secs\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n

Prev Up Next
probe::netfilter.arp.out Home probe::netfilter.bridge.local_in
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-in.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-in.html", "unified_diff": "@@ -1,67 +1,67 @@\n probe::netfilter.bridge.local_in
probe::netfilter.bridge.local_in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.local_in — \n Called on a bridging packet destined for the local computer\n-

Synopsis

netfilter.bridge.local_in

Values

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

br_poid

\n- Port identifier\n-

br_bid

\n- Identity of bridge\n-

llcproto_stp

\n- Constant used to signify Bridge Spanning Tree Protocol packet\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n+

Synopsis

netfilter.bridge.local_in

Values

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

data_str

\n+ A string representing the packet buffer contents\n+

length

\n+ The length of the packet buffer contents, in bytes\n

outdev_name

\n Name of network device packet will be routed to (if known)\n-

br_flags

\n- BPDU flags\n-

protocol

\n- Packet protocol\n-

br_htime

\n- Hello time in 1/256 secs\n+

br_rid

\n+ Identity of root bridge\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

br_mac

\n- Bridge MAC address\n

nf_accept

\n Constant used to signify an 'accept' verdict\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

br_rmac

\n+ Root bridge MAC address\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

br_vid

\n+ Protocol version identifier\n+

llcproto_stp

\n+ Constant used to signify Bridge Spanning Tree Protocol packet\n

outdev

\n Address of net_device representing output device, 0 if unknown\n-

br_type

\n- BPDU type\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

br_cost

\n- Total cost from transmitting bridge to root\n

br_msg

\n Message age in 1/256 secs\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

data_str

\n- A string representing the packet buffer contents\n+

br_fd

\n+ Forward delay in 1/256 secs\n+

br_mac

\n+ Bridge MAC address\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

br_cost

\n+ Total cost from transmitting bridge to root\n+

br_poid

\n+ Port identifier\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

brhdr

\n+ Address of bridge header\n+

br_bid

\n+ Identity of bridge\n+

br_type

\n+ BPDU type\n+

br_flags

\n+ BPDU flags\n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

br_max

\n+ Max age in 1/256 secs\n

br_prid

\n Protocol identifier\n-

length

\n- The length of the packet buffer contents, in bytes\n+

protocol

\n+ Packet protocol\n+

br_htime

\n+ Hello time in 1/256 secs\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n

pf

\n Protocol family -- always “bridge”\n-

br_fd

\n- Forward delay in 1/256 secs\n

llcpdu

\n Address of LLC Protocol Data Unit\n-

br_rmac

\n- Root bridge MAC address\n-

br_rid

\n- Identity of root bridge\n-

br_max

\n- Max age in 1/256 secs\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n-

brhdr

\n- Address of bridge header\n-

br_vid

\n- Protocol version identifier\n

Prev Up Next
probe::netfilter.bridge.forward Home probe::netfilter.bridge.local_out
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-out.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-out.html", "unified_diff": "@@ -1,67 +1,67 @@\n probe::netfilter.bridge.local_out
probe::netfilter.bridge.local_out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.local_out — \n Called on a bridging packet coming from a local process\n-

Synopsis

netfilter.bridge.local_out

Values

br_htime

\n- Hello time in 1/256 secs\n-

protocol

\n- Packet protocol\n+

Synopsis

netfilter.bridge.local_out

Values

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

br_rmac

\n+ Root bridge MAC address\n+

br_vid

\n+ Protocol version identifier\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

data_str

\n+ A string representing the packet buffer contents\n+

length

\n+ The length of the packet buffer contents, in bytes\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

br_rid

\n+ Identity of root bridge\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n

nf_accept

\n Constant used to signify an 'accept' verdict\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

br_poid

\n+ Port identifier\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

br_cost

\n+ Total cost from transmitting bridge to root\n

br_mac

\n Bridge MAC address\n+

llcproto_stp

\n+ Constant used to signify Bridge Spanning Tree Protocol packet\n

outdev

\n Address of net_device representing output device, 0 if unknown\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

br_type

\n- BPDU type\n

br_msg

\n Message age in 1/256 secs\n-

br_cost

\n- Total cost from transmitting bridge to root\n-

data_str

\n- A string representing the packet buffer contents\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

br_bid

\n- Identity of bridge\n-

llcproto_stp

\n- Constant used to signify Bridge Spanning Tree Protocol packet\n-

br_poid

\n- Port identifier\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n+

br_fd

\n+ Forward delay in 1/256 secs\n

br_flags

\n BPDU flags\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

br_rid

\n- Identity of root bridge\n-

br_rmac

\n- Root bridge MAC address\n-

br_max

\n- Max age in 1/256 secs\n

indev_name

\n Name of network device packet was received on (if known)\n+

br_max

\n+ Max age in 1/256 secs\n+

br_bid

\n+ Identity of bridge\n+

br_type

\n+ BPDU type\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n

brhdr

\n Address of bridge header\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n-

br_vid

\n- Protocol version identifier\n+

llcpdu

\n+ Address of LLC Protocol Data Unit\n+

br_htime

\n+ Hello time in 1/256 secs\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n

pf

\n Protocol family -- always “bridge”\n

br_prid

\n Protocol identifier\n-

length

\n- The length of the packet buffer contents, in bytes\n-

br_fd

\n- Forward delay in 1/256 secs\n-

llcpdu

\n- Address of LLC Protocol Data Unit\n+

protocol

\n+ Packet protocol\n

Prev Up Next
probe::netfilter.bridge.local_in Home probe::netfilter.bridge.post_routing
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-post-routing.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-post-routing.html", "unified_diff": "@@ -1,67 +1,67 @@\n probe::netfilter.bridge.post_routing
probe::netfilter.bridge.post_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.post_routing — \n - Called before a bridging packet hits the wire\n-

Synopsis

netfilter.bridge.post_routing

Values

br_rmac

\n- Root bridge MAC address\n-

br_rid

\n- Identity of root bridge\n-

br_max

\n- Max age in 1/256 secs\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

brhdr

\n- Address of bridge header\n+

Synopsis

netfilter.bridge.post_routing

Values

br_vid

\n+ Protocol version identifier\n

nf_drop

\n Constant used to signify a 'drop' verdict\n-

br_vid

\n- Protocol version identifier\n-

pf

\n- Protocol family -- always “bridge”\n-

br_prid

\n- Protocol identifier\n-

length

\n- The length of the packet buffer contents, in bytes\n-

br_fd

\n- Forward delay in 1/256 secs\n-

llcpdu

\n- Address of LLC Protocol Data Unit\n-

protocol

\n- Packet protocol\n-

br_htime

\n- Hello time in 1/256 secs\n+

br_rmac

\n+ Root bridge MAC address\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n

nf_accept

\n Constant used to signify an 'accept' verdict\n+

length

\n+ The length of the packet buffer contents, in bytes\n+

data_str

\n+ A string representing the packet buffer contents\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

br_rid

\n+ Identity of root bridge\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

br_poid

\n+ Port identifier\n+

br_cost

\n+ Total cost from transmitting bridge to root\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n

br_mac

\n Bridge MAC address\n+

br_fd

\n+ Forward delay in 1/256 secs\n

outdev

\n Address of net_device representing output device, 0 if unknown\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

br_type

\n- BPDU type\n

br_msg

\n Message age in 1/256 secs\n-

br_cost

\n- Total cost from transmitting bridge to root\n-

data_str

\n- A string representing the packet buffer contents\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

br_bid

\n- Identity of bridge\n

llcproto_stp

\n Constant used to signify Bridge Spanning Tree Protocol packet\n-

br_poid

\n- Port identifier\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n+

br_max

\n+ Max age in 1/256 secs\n+

indev_name

\n+ Name of network device packet was received on (if known)\n

br_flags

\n BPDU flags\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n+

br_type

\n+ BPDU type\n+

br_bid

\n+ Identity of bridge\n+

brhdr

\n+ Address of bridge header\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

llcpdu

\n+ Address of LLC Protocol Data Unit\n+

pf

\n+ Protocol family -- always “bridge”\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n+

br_htime

\n+ Hello time in 1/256 secs\n+

protocol

\n+ Packet protocol\n+

br_prid

\n+ Protocol identifier\n

Prev Up Next
probe::netfilter.bridge.local_out Home probe::netfilter.bridge.pre_routing
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-pre-routing.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-pre-routing.html", "unified_diff": "@@ -1,67 +1,67 @@\n probe::netfilter.bridge.pre_routing
probe::netfilter.bridge.pre_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.pre_routing — \n - Called before a bridging packet is routed\n-

Synopsis

netfilter.bridge.pre_routing

Values

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n+

Synopsis

netfilter.bridge.pre_routing

Values

brhdr

\n+ Address of bridge header\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

br_max

\n+ Max age in 1/256 secs\n+

indev_name

\n+ Name of network device packet was received on (if known)\n

br_flags

\n BPDU flags\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n+

br_type

\n+ BPDU type\n

br_bid

\n Identity of bridge\n-

llcproto_stp

\n- Constant used to signify Bridge Spanning Tree Protocol packet\n-

br_poid

\n- Port identifier\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

br_mac

\n- Bridge MAC address\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n

protocol

\n Packet protocol\n+

br_prid

\n+ Protocol identifier\n+

llcpdu

\n+ Address of LLC Protocol Data Unit\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n+

pf

\n+ Protocol family -- always “bridge”\n

br_htime

\n Hello time in 1/256 secs\n-

br_msg

\n- Message age in 1/256 secs\n-

br_cost

\n- Total cost from transmitting bridge to root\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n

data_str

\n A string representing the packet buffer contents\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

br_type

\n- BPDU type\n-

pf

\n- Protocol family -- always “bridge”\n-

br_prid

\n- Protocol identifier\n

length

\n The length of the packet buffer contents, in bytes\n-

llcpdu

\n- Address of LLC Protocol Data Unit\n-

br_fd

\n- Forward delay in 1/256 secs\n-

br_max

\n- Max age in 1/256 secs\n

br_rid

\n Identity of root bridge\n-

br_rmac

\n- Root bridge MAC address\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n

br_vid

\n Protocol version identifier\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

brhdr

\n- Address of bridge header\n

nf_drop

\n Constant used to signify a 'drop' verdict\n+

br_rmac

\n+ Root bridge MAC address\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

br_mac

\n+ Bridge MAC address\n+

br_fd

\n+ Forward delay in 1/256 secs\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

br_msg

\n+ Message age in 1/256 secs\n+

llcproto_stp

\n+ Constant used to signify Bridge Spanning Tree Protocol packet\n+

br_poid

\n+ Port identifier\n+

br_cost

\n+ Total cost from transmitting bridge to root\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n

Prev Up Next
probe::netfilter.bridge.post_routing Home probe::netfilter.ip.forward
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-forward.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-forward.html", "unified_diff": "@@ -1,61 +1,61 @@\n probe::netfilter.ip.forward
probe::netfilter.ip.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.forward — \n Called on an incoming IP packet addressed to some other computer\n-

Synopsis

netfilter.ip.forward

Values

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

iphdr

\n+

Synopsis

netfilter.ip.forward

Values

iphdr

\n Address of IP header\n-

ipproto_udp

\n- Constant used to signify that the packet protocol is UDP\n-

ipproto_tcp

\n- Constant used to signify that the packet protocol is TCP\n+

saddr

\n+ A string representing the source IP address\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n

syn

\n TCP SYN flag (if protocol is TCP; ipv4 only)\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ack

\n- TCP ACK flag (if protocol is TCP; ipv4 only)\n+

rst

\n+ TCP RST flag (if protocol is TCP; ipv4 only)\n+

ipproto_udp

\n+ Constant used to signify that the packet protocol is UDP\n+

indev_name

\n+ Name of network device packet was received on (if known)\n

protocol

\n Packet protocol from driver (ipv4 only)\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n+

pf

\n+ Protocol family -- either “ipv4” or “ipv6”\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n+

dport

\n+ TCP or UDP destination port (ipv4 only)\n+

family

\n+ IP address family\n

nf_queue

\n Constant used to signify a 'queue' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

sport

\n- TCP or UDP source port (ipv4 only)\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

urg

\n- TCP URG flag (if protocol is TCP; ipv4 only)\n

psh

\n TCP PSH flag (if protocol is TCP; ipv4 only)\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n

data_str

\n A string representing the packet buffer contents\n-

dport

\n- TCP or UDP destination port (ipv4 only)\n-

family

\n- IP address family\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

pf

\n- Protocol family -- either “ipv4” or “ipv6”\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n

length

\n The length of the packet buffer contents, in bytes\n+

sport

\n+ TCP or UDP source port (ipv4 only)\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n

fin

\n TCP FIN flag (if protocol is TCP; ipv4 only)\n-

saddr

\n- A string representing the source IP address\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

rst

\n- TCP RST flag (if protocol is TCP; ipv4 only)\n

nf_drop

\n Constant used to signify a 'drop' verdict\n+

urg

\n+ TCP URG flag (if protocol is TCP; ipv4 only)\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

ipproto_tcp

\n+ Constant used to signify that the packet protocol is TCP\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

ack

\n+ TCP ACK flag (if protocol is TCP; ipv4 only)\n

daddr

\n A string representing the destination IP address\n

Prev Up Next
probe::netfilter.bridge.pre_routing Home probe::netfilter.ip.local_in
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-in.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-in.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,61 +1,61 @@\n probe::netfilter.ip.local_in
probe::netfilter.ip.local_in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.local_in — \n Called on an incoming IP packet addressed to the local computer\n

Synopsis

netfilter.ip.local_in

Values

protocol

\n Packet protocol from driver (ipv4 only)\n-

ack

\n- TCP ACK flag (if protocol is TCP; ipv4 only)\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

sport

\n- TCP or UDP source port (ipv4 only)\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

urg

\n- TCP URG flag (if protocol is TCP; ipv4 only)\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

psh

\n- TCP PSH flag (if protocol is TCP; ipv4 only)\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n

family

\n IP address family\n-

data_str

\n- A string representing the packet buffer contents\n+

pf

\n+ Protocol family -- either “ipv4” or “ipv6”\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n

dport

\n TCP or UDP destination port (ipv4 only)\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n-

ipproto_udp

\n- Constant used to signify that the packet protocol is UDP\n-

iphdr

\n- Address of IP header\n-

ipproto_tcp

\n- Constant used to signify that the packet protocol is TCP\n

syn

\n TCP SYN flag (if protocol is TCP; ipv4 only)\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

fin

\n- TCP FIN flag (if protocol is TCP; ipv4 only)\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n

saddr

\n A string representing the source IP address\n+

iphdr

\n+ Address of IP header\n+

ipproto_udp

\n+ Constant used to signify that the packet protocol is UDP\n

indev_name

\n Name of network device packet was received on (if known)\n

rst

\n TCP RST flag (if protocol is TCP; ipv4 only)\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n+

ipproto_tcp

\n+ Constant used to signify that the packet protocol is TCP\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n

daddr

\n A string representing the destination IP address\n+

ack

\n+ TCP ACK flag (if protocol is TCP; ipv4 only)\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n+

sport

\n+ TCP or UDP source port (ipv4 only)\n

length

\n The length of the packet buffer contents, in bytes\n-

pf

\n- Protocol family -- either “ipv4” or “ipv6”\n+

data_str

\n+ A string representing the packet buffer contents\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

psh

\n+ TCP PSH flag (if protocol is TCP; ipv4 only)\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

urg

\n+ TCP URG flag (if protocol is TCP; ipv4 only)\n+

fin

\n+ TCP FIN flag (if protocol is TCP; ipv4 only)\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n

Prev Up Next
probe::netfilter.ip.forward Home probe::netfilter.ip.local_out
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-out.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-out.html", "unified_diff": "@@ -1,61 +1,61 @@\n probe::netfilter.ip.local_out
probe::netfilter.ip.local_out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.local_out — \n Called on an outgoing IP packet\n-

Synopsis

netfilter.ip.local_out

Values

daddr

\n- A string representing the destination IP address\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

saddr

\n- A string representing the source IP address\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n-

rst

\n- TCP RST flag (if protocol is TCP; ipv4 only)\n-

fin

\n- TCP FIN flag (if protocol is TCP; ipv4 only)\n-

length

\n- The length of the packet buffer contents, in bytes\n-

pf

\n- Protocol family -- either “ipv4” or “ipv6”\n-

psh

\n- TCP PSH flag (if protocol is TCP; ipv4 only)\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n+

Synopsis

netfilter.ip.local_out

Values

protocol

\n+ Packet protocol from driver (ipv4 only)\n

family

\n IP address family\n

dport

\n TCP or UDP destination port (ipv4 only)\n-

data_str

\n- A string representing the packet buffer contents\n-

sport

\n- TCP or UDP source port (ipv4 only)\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

urg

\n- TCP URG flag (if protocol is TCP; ipv4 only)\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

protocol

\n- Packet protocol from driver (ipv4 only)\n-

ack

\n- TCP ACK flag (if protocol is TCP; ipv4 only)\n+

pf

\n+ Protocol family -- either “ipv4” or “ipv6”\n

nf_stop

\n Constant used to signify a 'stop' verdict\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ipproto_tcp

\n- Constant used to signify that the packet protocol is TCP\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n

syn

\n TCP SYN flag (if protocol is TCP; ipv4 only)\n-

ipproto_udp

\n- Constant used to signify that the packet protocol is UDP\n

iphdr

\n Address of IP header\n+

saddr

\n+ A string representing the source IP address\n+

ipproto_udp

\n+ Constant used to signify that the packet protocol is UDP\n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

rst

\n+ TCP RST flag (if protocol is TCP; ipv4 only)\n+

ipproto_tcp

\n+ Constant used to signify that the packet protocol is TCP\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

daddr

\n+ A string representing the destination IP address\n

data_hex

\n A hexadecimal string representing the packet buffer contents\n+

ack

\n+ TCP ACK flag (if protocol is TCP; ipv4 only)\n+

data_str

\n+ A string representing the packet buffer contents\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

length

\n+ The length of the packet buffer contents, in bytes\n+

sport

\n+ TCP or UDP source port (ipv4 only)\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

psh

\n+ TCP PSH flag (if protocol is TCP; ipv4 only)\n+

fin

\n+ TCP FIN flag (if protocol is TCP; ipv4 only)\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

urg

\n+ TCP URG flag (if protocol is TCP; ipv4 only)\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n

Prev Up Next
probe::netfilter.ip.local_in Home probe::netfilter.ip.post_routing
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-post-routing.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-post-routing.html", "unified_diff": "@@ -1,61 +1,61 @@\n probe::netfilter.ip.post_routing
probe::netfilter.ip.post_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.post_routing — \n Called immediately before an outgoing IP packet leaves the computer\n-

Synopsis

netfilter.ip.post_routing

Values

daddr

\n- A string representing the destination IP address\n+

Synopsis

netfilter.ip.post_routing

Values

iphdr

\n+ Address of IP header\n+

saddr

\n+ A string representing the source IP address\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

syn

\n+ TCP SYN flag (if protocol is TCP; ipv4 only)\n

rst

\n TCP RST flag (if protocol is TCP; ipv4 only)\n-

nf_drop

\n- Constant used to signify a 'drop' verdict\n+

ipproto_udp

\n+ Constant used to signify that the packet protocol is UDP\n

indev_name

\n Name of network device packet was received on (if known)\n-

saddr

\n- A string representing the source IP address\n-

fin

\n- TCP FIN flag (if protocol is TCP; ipv4 only)\n+

protocol

\n+ Packet protocol from driver (ipv4 only)\n

pf

\n Protocol family -- either “ipv4” or “ipv6”\n-

length

\n- The length of the packet buffer contents, in bytes\n+

nf_stop

\n+ Constant used to signify a 'stop' verdict\n

dport

\n TCP or UDP destination port (ipv4 only)\n-

data_str

\n- A string representing the packet buffer contents\n

family

\n IP address family\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n

psh

\n TCP PSH flag (if protocol is TCP; ipv4 only)\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n-

urg

\n- TCP URG flag (if protocol is TCP; ipv4 only)\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n-

sport

\n- TCP or UDP source port (ipv4 only)\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n

nf_queue

\n Constant used to signify a 'queue' verdict\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n

nf_stolen

\n Constant used to signify a 'stolen' verdict\n-

ack

\n- TCP ACK flag (if protocol is TCP; ipv4 only)\n-

protocol

\n- Packet protocol from driver (ipv4 only)\n+

length

\n+ The length of the packet buffer contents, in bytes\n+

data_str

\n+ A string representing the packet buffer contents\n

outdev_name

\n Name of network device packet will be routed to (if known)\n-

nf_stop

\n- Constant used to signify a 'stop' verdict\n-

syn

\n- TCP SYN flag (if protocol is TCP; ipv4 only)\n+

sport

\n+ TCP or UDP source port (ipv4 only)\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

nf_drop

\n+ Constant used to signify a 'drop' verdict\n+

fin

\n+ TCP FIN flag (if protocol is TCP; ipv4 only)\n+

urg

\n+ TCP URG flag (if protocol is TCP; ipv4 only)\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n

ipproto_tcp

\n Constant used to signify that the packet protocol is TCP\n-

iphdr

\n- Address of IP header\n-

ipproto_udp

\n- Constant used to signify that the packet protocol is UDP\n

data_hex

\n A hexadecimal string representing the packet buffer contents\n+

ack

\n+ TCP ACK flag (if protocol is TCP; ipv4 only)\n+

daddr

\n+ A string representing the destination IP address\n

Prev Up Next
probe::netfilter.ip.local_out Home probe::netfilter.ip.pre_routing
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-pre-routing.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-pre-routing.html", "unified_diff": "@@ -1,61 +1,61 @@\n probe::netfilter.ip.pre_routing
probe::netfilter.ip.pre_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.pre_routing — \n Called before an IP packet is routed\n-

Synopsis

netfilter.ip.pre_routing

Values

ipproto_udp

\n- Constant used to signify that the packet protocol is UDP\n-

iphdr

\n- Address of IP header\n-

data_hex

\n- A hexadecimal string representing the packet buffer contents\n+

Synopsis

netfilter.ip.pre_routing

Values

protocol

\n+ Packet protocol from driver (ipv4 only)\n

nf_stop

\n Constant used to signify a 'stop' verdict\n-

outdev_name

\n- Name of network device packet will be routed to (if known)\n-

ipproto_tcp

\n- Constant used to signify that the packet protocol is TCP\n+

pf

\n+ Protocol family - either 'ipv4' or 'ipv6'\n+

dport

\n+ TCP or UDP destination port (ipv4 only)\n+

family

\n+ IP address family\n+

saddr

\n+ A string representing the source IP address\n+

iphdr

\n+ Address of IP header\n

syn

\n TCP SYN flag (if protocol is TCP; ipv4 only)\n-

nf_queue

\n- Constant used to signify a 'queue' verdict\n-

nf_stolen

\n- Constant used to signify a 'stolen' verdict\n-

nf_accept

\n- Constant used to signify an 'accept' verdict\n-

protocol

\n- Packet protocol from driver (ipv4 only)\n+

indev

\n+ Address of net_device representing input device, 0 if unknown\n+

rst

\n+ TCP RST flag (if protocol is TCP; ipv4 only)\n+

indev_name

\n+ Name of network device packet was received on (if known)\n+

ipproto_udp

\n+ Constant used to signify that the packet protocol is UDP\n+

outdev

\n+ Address of net_device representing output device, 0 if unknown\n+

ipproto_tcp

\n+ Constant used to signify that the packet protocol is TCP\n

ack

\n TCP ACK flag (if protocol is TCP; ipv4 only)\n+

data_hex

\n+ A hexadecimal string representing the packet buffer contents\n+

daddr

\n+ A string representing the destination IP address\n

psh

\n TCP PSH flag (if protocol is TCP; ipv4 only)\n-

family

\n- IP address family\n-

nf_repeat

\n- Constant used to signify a 'repeat' verdict\n-

dport

\n- TCP or UDP destination port (ipv4 only)\n-

data_str

\n- A string representing the packet buffer contents\n-

outdev

\n- Address of net_device representing output device, 0 if unknown\n+

nf_queue

\n+ Constant used to signify a 'queue' verdict\n+

nf_accept

\n+ Constant used to signify an 'accept' verdict\n+

nf_stolen

\n+ Constant used to signify a 'stolen' verdict\n

sport

\n TCP or UDP source port (ipv4 only)\n-

urg

\n- TCP URG flag (if protocol is TCP; ipv4 only)\n-

indev

\n- Address of net_device representing input device, 0 if unknown\n

length

\n The length of the packet buffer contents, in bytes\n-

pf

\n- Protocol family - either 'ipv4' or 'ipv6'\n+

data_str

\n+ A string representing the packet buffer contents\n+

outdev_name

\n+ Name of network device packet will be routed to (if known)\n+

nf_repeat

\n+ Constant used to signify a 'repeat' verdict\n+

urg

\n+ TCP URG flag (if protocol is TCP; ipv4 only)\n

fin

\n TCP FIN flag (if protocol is TCP; ipv4 only)\n-

daddr

\n- A string representing the destination IP address\n-

saddr

\n- A string representing the source IP address\n-

indev_name

\n- Name of network device packet was received on (if known)\n-

rst

\n- TCP RST flag (if protocol is TCP; ipv4 only)\n

nf_drop

\n Constant used to signify a 'drop' verdict\n

Prev Up Next
probe::netfilter.ip.post_routing Home probe::sunrpc.clnt.bind_new_program
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readahead.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readahead.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.aop.readahead
probe::nfs.aop.readahead
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readahead — \n NFS client reading multiple pages\n-

Synopsis

nfs.aop.readahead

Values

rpages

\n- read size (in pages)\n-

nr_pages

\n- number of pages attempted to read in this execution\n+

Synopsis

nfs.aop.readahead

Values

file

\n+ filp argument\n+

dev

\n+ device identifier\n

ino

\n inode number\n-

file

\n- filp argument\n

rsize

\n read size (in bytes)\n-

dev

\n- device identifier\n+

nr_pages

\n+ number of pages attempted to read in this execution\n

size

\n number of pages attempted to read in this execution\n+

rpages

\n+ read size (in pages)\n

Description

\n Fires when in readahead way, read several pages once\n

Prev Up Next
probe:: Home probe::nfs.aop.readpage
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpage.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpage.html", "unified_diff": "@@ -1,27 +1,27 @@\n probe::nfs.aop.readpage
probe::nfs.aop.readpage
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readpage — \n NFS client synchronously reading a page\n-

Synopsis

nfs.aop.readpage

Values

sb_flag

\n- super block flags\n-

__page

\n- the address of page\n-

ino

\n+

Synopsis

nfs.aop.readpage

Values

ino

\n inode number\n+

sb_flag

\n+ super block flags\n+

dev

\n+ device identifier\n

file

\n file argument\n+

i_flag

\n+ file flags\n+

size

\n+ number of pages to be read in this execution \n

page_index

\n offset within mapping, can used a page identifier\n and position identifier in the page frame\n-

i_flag

\n- file flags\n+

__page

\n+ the address of page\n

i_size

\n file length in bytes\n

rsize

\n read size (in bytes)\n-

dev

\n- device identifier\n-

size

\n- number of pages to be read in this execution \n

Description

\n Read the page over, only fires when a previous async\n read operation failed\n

Prev Up Next
probe::nfs.aop.readahead Home probe::nfs.aop.readpages
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpages.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpages.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.aop.readpages
probe::nfs.aop.readpages
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readpages — \n NFS client reading multiple pages\n

Synopsis

nfs.aop.readpages

Values

rsize

\n read size (in bytes)\n-

dev

\n- device identifier\n-

size

\n- number of pages attempted to read in this execution\n

nr_pages

\n number of pages attempted to read in this execution\n-

ino

\n- inode number \n-

file

\n- filp argument\n+

size

\n+ number of pages attempted to read in this execution\n

rpages

\n read size (in pages)\n+

dev

\n+ device identifier\n+

file

\n+ filp argument\n+

ino

\n+ inode number \n

Description

\n Fires when in readahead way, read several pages once\n

Prev Up Next
probe::nfs.aop.readpage Home probe::nfs.aop.release_page
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-release-page.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-release-page.html", "unified_diff": "@@ -1,16 +1,16 @@\n probe::nfs.aop.release_page
probe::nfs.aop.release_page
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.release_page — \n NFS client releasing page\n-

Synopsis

nfs.aop.release_page

Values

ino

\n- inode number\n-

__page

\n+

Synopsis

nfs.aop.release_page

Values

__page

\n the address of page\n+

size

\n+ release pages\n

page_index

\n offset within mapping, can used a page identifier\n and position identifier in the page frame\n-

size

\n- release pages\n

dev

\n device identifier\n+

ino

\n+ inode number\n

Description

\n Fires when do a release operation on NFS.\n

Prev Up Next
probe::nfs.aop.readpages Home probe::nfs.aop.set_page_dirty
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-set-page-dirty.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-set-page-dirty.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::nfs.aop.set_page_dirty
probe::nfs.aop.set_page_dirty
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.set_page_dirty — \n NFS client marking page as dirty\n-

Synopsis

nfs.aop.set_page_dirty

Values

page_flag

\n- page flags\n-

__page

\n+

Synopsis

nfs.aop.set_page_dirty

Values

__page

\n the address of page\n+

page_flag

\n+ page flags\n

Description

\n This probe attaches to the generic __set_page_dirty_nobuffers function.\n Thus, this probe is going to fire on many other file systems in\n addition to the NFS client.\n

Prev Up Next
probe::nfs.aop.release_page Home probe::nfs.aop.write_begin
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-begin.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-begin.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::nfs.aop.write_begin
probe::nfs.aop.write_begin
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.write_begin — \n NFS client begin to write data\n-

Synopsis

nfs.aop.write_begin

Values

size

\n- write bytes\n+

Synopsis

nfs.aop.write_begin

Values

ino

\n+ inode number \n+

offset

\n+ start address of this write operation \n

dev

\n device identifier\n+

size

\n+ write bytes\n

page_index

\n offset within mapping, can used a page identifier\n and position identifier in the page frame\n-

offset

\n- start address of this write operation \n

to

\n end address of this write operation \n-

ino

\n- inode number \n

__page

\n the address of page\n

Description

\n Occurs when write operation occurs on nfs. It prepare a page for writing,\n look for a request corresponding to the page. If there\n is one, and it belongs to another file, it flush it out\n before it tries to copy anything into the page. \n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-end.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-end.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,29 +1,29 @@\n probe::nfs.aop.write_end

probe::nfs.aop.write_end
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.write_end — \n NFS client complete writing data\n

Synopsis

nfs.aop.write_end

Values

size

\n write bytes\n-

dev

\n- device identifier\n-

i_flag

\n- file flags\n

page_index

\n offset within mapping, can used a page identifier and position identifier in the page frame\n

i_size

\n file length in bytes\n-

offset

\n- start address of this write operation\n

to

\n end address of this write operation\n

__page

\n the address of page\n-

ino

\n- inode number\n

sb_flag

\n super block flags\n+

ino

\n+ inode number\n+

offset

\n+ start address of this write operation\n+

i_flag

\n+ file flags\n+

dev

\n+ device identifier\n

Description

\n Fires when do a write operation on nfs,\n often after prepare_write\n

\n \n Update and possibly write a cached page of an NFS file.\n

Prev Up Next
probe::nfs.aop.write_begin Home probe::nfs.aop.writepage
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepage.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepage.html", "unified_diff": "@@ -1,33 +1,33 @@\n probe::nfs.aop.writepage
probe::nfs.aop.writepage
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.writepage — \n NFS client writing a mapped page to the NFS server\n-

Synopsis

nfs.aop.writepage

Values

size

\n+

Synopsis

nfs.aop.writepage

Values

wsize

\n+ write size\n+

page_index

\n+ offset within mapping,\n+ can used a page identifier and position identifier in the page frame\n+

size

\n number of pages to be written in this execution\n-

dev

\n- device identifier\n

for_kupdate

\n a flag of writeback_control,\n indicates if it's a kupdate writeback\n-

i_state

\n- inode state flags\n+

for_reclaim

\n+ a flag of writeback_control,\n+ indicates if it's invoked from the page allocator\n

__page

\n the address of page\n-

ino

\n- inode number \n

i_size

\n file length in bytes\n-

page_index

\n- offset within mapping,\n- can used a page identifier and position identifier in the page frame\n-

i_flag

\n- file flags\n-

for_reclaim

\n- a flag of writeback_control,\n- indicates if it's invoked from the page allocator\n+

i_state

\n+ inode state flags\n+

ino

\n+ inode number \n

sb_flag

\n super block flags\n-

wsize

\n- write size\n+

dev

\n+ device identifier\n+

i_flag

\n+ file flags\n

Description

\n The priority of wb is decided by the flags\n for_reclaim and for_kupdate.\n

Prev Up Next
probe::nfs.aop.write_end Home probe::nfs.aop.writepages
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepages.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepages.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::nfs.aop.writepages
probe::nfs.aop.writepages
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.writepages — \n NFS client writing several dirty pages to the NFS server\n-

Synopsis

nfs.aop.writepages

Values

for_reclaim

\n- a flag of writeback_control,\n- indicates if it's invoked from the page allocator\n-

wsize

\n+

Synopsis

nfs.aop.writepages

Values

wsize

\n write size\n-

nr_to_write

\n- number of pages attempted to be written in this execution\n

for_kupdate

\n a flag of writeback_control,\n indicates if it's a kupdate writeback\n-

dev

\n- device identifier\n

size

\n number of pages attempted to be written in this execution\n

wpages

\n write size (in pages)\n+

for_reclaim

\n+ a flag of writeback_control,\n+ indicates if it's invoked from the page allocator\n

ino

\n inode number\n+

nr_to_write

\n+ number of pages attempted to be written in this execution\n+

dev

\n+ device identifier\n

Description

\n The priority of wb is decided by the flags\n for_reclaim and for_kupdate.\n

Prev Up Next
probe::nfs.aop.writepage Home probe::nfs.fop.aio_read
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-read.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::nfs.fop.aio_read
probe::nfs.fop.aio_read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.aio_read — \n NFS client aio_read file operation\n-

Synopsis

nfs.fop.aio_read

Values

cache_time

\n- when we started read-caching this inode\n+

Synopsis

nfs.fop.aio_read

Values

file_name

\n+ file name\n

dev

\n device identifier\n-

cache_valid

\n- cache related bit mask flag\n

pos

\n current position of file \n-

ino

\n- inode number \n+

cache_valid

\n+ cache related bit mask flag\n+

parent_name

\n+ parent dir name\n+

cache_time

\n+ when we started read-caching this inode\n

attrtimeo

\n how long the cached information is assumed to be valid.\n We need to revalidate the cached attrs for this inode\n if jiffies - read_cache_jiffies > attrtimeo.\n-

parent_name

\n- parent dir name\n

count

\n read bytes\n

buf

\n the address of buf in user space\n-

file_name

\n- file name\n+

ino

\n+ inode number \n

Prev Up Next
probe::nfs.aop.writepages Home probe::nfs.fop.aio_write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-write.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::nfs.fop.aio_write
probe::nfs.fop.aio_write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.aio_write — \n NFS client aio_write file operation\n-

Synopsis

nfs.fop.aio_write

Values

dev

\n- device identifier\n-

pos

\n- offset of the file \n+

Synopsis

nfs.fop.aio_write

Values

ino

\n+ inode number \n+

count

\n+ read bytes\n

buf

\n the address of buf in user space\n-

file_name

\n- file name\n-

ino

\n- inode number \n

parent_name

\n parent dir name\n-

count

\n- read bytes\n+

pos

\n+ offset of the file \n+

dev

\n+ device identifier\n+

file_name

\n+ file name\n

Prev Up Next
probe::nfs.fop.aio_read Home probe::nfs.fop.check_flags
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-flush.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-flush.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::nfs.fop.flush
probe::nfs.fop.flush
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.flush — \n NFS client flush file operation\n-

Synopsis

nfs.fop.flush

Values

dev

\n- device identifier\n-

ino

\n- inode number\n-

mode

\n+

Synopsis

nfs.fop.flush

Values

mode

\n file mode\n

ndirty

\n number of dirty page\n+

ino

\n+ inode number\n+

dev

\n+ device identifier\n

Prev Up Next
probe::nfs.fop.check_flags Home probe::nfs.fop.fsync
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-fsync.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-fsync.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::nfs.fop.fsync
probe::nfs.fop.fsync
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.fsync — \n NFS client fsync operation\n-

Synopsis

nfs.fop.fsync

Values

dev

\n- device identifier\n+

Synopsis

nfs.fop.fsync

Values

ndirty

\n+ number of dirty pages\n

ino

\n inode number\n-

ndirty

\n- number of dirty pages\n+

dev

\n+ device identifier\n

Prev Up Next
probe::nfs.fop.flush Home probe::nfs.fop.llseek
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-llseek.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-llseek.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::nfs.fop.llseek
probe::nfs.fop.llseek
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.llseek — \n NFS client llseek operation\n-

Synopsis

nfs.fop.llseek

Values

dev

\n+

Synopsis

nfs.fop.llseek

Values

whence_str

\n+ symbolic string representation of the position to seek from\n+

offset

\n+ the offset of the file will be repositioned\n+

dev

\n device identifier\n

ino

\n inode number\n

whence

\n the position to seek from\n-

offset

\n- the offset of the file will be repositioned\n-

whence_str

\n- symbolic string representation of the position to seek from\n

Prev Up Next
probe::nfs.fop.fsync Home probe::nfs.fop.lock
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-lock.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-lock.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.fop.lock
probe::nfs.fop.lock
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.lock — \n NFS client file lock operation\n-

Synopsis

nfs.fop.lock

Values

dev

\n- device identifier\n-

fl_end

\n+

Synopsis

nfs.fop.lock

Values

fl_end

\n ending offset of locked region\n-

cmd

\n- cmd arguments\n-

fl_flag

\n- lock flags\n

i_mode

\n file type and access rights\n-

ino

\n- inode number\n+

cmd

\n+ cmd arguments\n

fl_type

\n lock type\n

fl_start

\n starting offset of locked region\n+

dev

\n+ device identifier\n+

fl_flag

\n+ lock flags\n+

ino

\n+ inode number\n

Prev Up Next
probe::nfs.fop.llseek Home probe::nfs.fop.mmap
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-mmap.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-mmap.html", "unified_diff": "@@ -1,27 +1,27 @@\n probe::nfs.fop.mmap
probe::nfs.fop.mmap
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.mmap — \n NFS client mmap operation\n-

Synopsis

nfs.fop.mmap

Values

buf

\n- the address of buf in user space\n+

Synopsis

nfs.fop.mmap

Values

vm_flag

\n+ vm flags\n+

dev

\n+ device identifier\n+

file_name

\n+ file name\n

parent_name

\n parent dir name\n-

ino

\n- inode number \n+

cache_time

\n+ when we started read-caching this inode\n

vm_start

\n start address within vm_mm \n-

dev

\n- device identifier\n+

buf

\n+ the address of buf in user space\n+

ino

\n+ inode number \n

cache_valid

\n cache related bit mask flag\n-

file_name

\n- file name\n

attrtimeo

\n how long the cached information is assumed to be valid.\n We need to revalidate the cached attrs for this inode \n if jiffies - read_cache_jiffies > attrtimeo.\n

vm_end

\n the first byte after end address within vm_mm\n-

vm_flag

\n- vm flags\n-

cache_time

\n- when we started read-caching this inode\n

Prev Up Next
probe::nfs.fop.lock Home probe::nfs.fop.open
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-open.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-open.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::nfs.fop.open
probe::nfs.fop.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.open — \n NFS client file open operation\n-

Synopsis

nfs.fop.open

Values

file_name

\n- file name\n-

flag

\n- file flag\n+

Synopsis

nfs.fop.open

Values

i_size

\n+ file length in bytes \n

dev

\n device identifier\n-

i_size

\n- file length in bytes \n+

file_name

\n+ file name\n

ino

\n inode number\n+

flag

\n+ file flag\n

Prev Up Next
probe::nfs.fop.mmap Home probe::nfs.fop.read
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-read-iter.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-read-iter.html", "unified_diff": "@@ -1,23 +1,23 @@\n probe::nfs.fop.read_iter
probe::nfs.fop.read_iter
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.read_iter — \n NFS client read_iter file operation\n-

Synopsis

nfs.fop.read_iter

Values

dev

\n+

Synopsis

nfs.fop.read_iter

Values

pos

\n+ current position of file \n+

cache_valid

\n+ cache related bit mask flag\n+

dev

\n device identifier\n+

file_name

\n+ file name\n

cache_time

\n when we started read-caching this inode\n-

cache_valid

\n- cache related bit mask flag\n-

pos

\n- current position of file \n-

count

\n- read bytes\n-

parent_name

\n- parent dir name\n

attrtimeo

\n how long the cached information is assumed to be valid.\n We need to revalidate the cached attrs for this inode\n if jiffies - read_cache_jiffies > attrtimeo.\n+

parent_name

\n+ parent dir name\n

ino

\n inode number \n-

file_name

\n- file name\n+

count

\n+ read bytes\n

Prev Up Next
probe::nfs.fop.read Home probe::nfs.fop.release
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-release.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-release.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::nfs.fop.release
probe::nfs.fop.release
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.release — \n NFS client release page operation\n-

Synopsis

nfs.fop.release

Values

ino

\n- inode number\n-

mode

\n+

Synopsis

nfs.fop.release

Values

mode

\n file mode\n+

ino

\n+ inode number\n

dev

\n device identifier\n

Prev Up Next
probe::nfs.fop.read_iter Home probe::nfs.fop.sendfile
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-sendfile.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-sendfile.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.fop.sendfile
probe::nfs.fop.sendfile
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.sendfile — \n NFS client send file operation\n-

Synopsis

nfs.fop.sendfile

Values

cache_time

\n- when we started read-caching this inode\n-

ppos

\n- current position of file\n+

Synopsis

nfs.fop.sendfile

Values

count

\n+ read bytes\n

attrtimeo

\n how long the cached information is assumed to be valid.\n We need to revalidate the cached attrs for this inode\n if jiffies - read_cache_jiffies > attrtimeo.\n-

count

\n- read bytes\n-

dev

\n- device identifier\n+

ppos

\n+ current position of file\n

cache_valid

\n cache related bit mask flag\n

ino

\n inode number\n+

cache_time

\n+ when we started read-caching this inode\n+

dev

\n+ device identifier\n

Prev Up Next
probe::nfs.fop.release Home probe::nfs.fop.write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-write-iter.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-write-iter.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::nfs.fop.write_iter
probe::nfs.fop.write_iter
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.write_iter — \n NFS client write_iter file operation\n-

Synopsis

nfs.fop.write_iter

Values

dev

\n- device identifier\n-

pos

\n- offset of the file \n-

file_name

\n- file name\n-

count

\n+

Synopsis

nfs.fop.write_iter

Values

count

\n read bytes\n-

parent_name

\n- parent dir name\n

ino

\n inode number \n+

parent_name

\n+ parent dir name\n+

dev

\n+ device identifier\n+

file_name

\n+ file name\n+

pos

\n+ offset of the file \n

Prev Up Next
probe::nfs.fop.write Home probe::nfs.proc.commit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-done.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-done.html", "unified_diff": "@@ -1,20 +1,20 @@\n probe::nfs.proc.commit_done
probe::nfs.proc.commit_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit_done — \n NFS client response to a commit RPC task\n-

Synopsis

nfs.proc.commit_done

Values

prot

\n- transfer protocol\n+

Synopsis

nfs.proc.commit_done

Values

status

\n+ result of last operation\n+

server_ip

\n+ IP address of server\n

timestamp

\n V4 timestamp, which is used for lease renewal\n-

count

\n- number of bytes committed\n-

version

\n- NFS version\n+

prot

\n+ transfer protocol\n

valid

\n fattr->valid, indicates which fields are valid \n-

server_ip

\n- IP address of server\n-

status

\n- result of last operation\n+

version

\n+ NFS version\n+

count

\n+ number of bytes committed\n

Description

\n Fires when a reply to a commit RPC task is received\n or some commit operation error occur (timeout or socket shutdown).\n

Prev Up Next
probe::nfs.proc.commit Home probe::nfs.proc.commit_setup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-setup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-setup.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::nfs.proc.commit_setup
probe::nfs.proc.commit_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit_setup — \n NFS client setting up a commit RPC task\n-

Synopsis

nfs.proc.commit_setup

Values

count

\n- bytes in this commit\n-

offset

\n- the file offset\n-

prot

\n- transfer protocol\n-

bitmask0

\n- V4 bitmask representing the set of attributes supported\n- on this filesystem\n-

bitmask1

\n+

Synopsis

nfs.proc.commit_setup

Values

bitmask1

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n+

prot

\n+ transfer protocol\n+

offset

\n+ the file offset\n

server_ip

\n IP address of server\n-

size

\n+

count

\n bytes in this commit\n+

bitmask0

\n+ V4 bitmask representing the set of attributes supported\n+ on this filesystem\n

version

\n NFS version\n+

size

\n+ bytes in this commit\n

Description

\n The commit_setup function is used to setup a commit RPC task.\n Is is not doing the actual commit operation.\n It does not exist in NFSv2.\n

Prev Up Next
probe::nfs.proc.commit_done Home probe::nfs.proc.create
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::nfs.proc.commit
probe::nfs.proc.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit — \n NFS client committing data on server\n-

Synopsis

nfs.proc.commit

Values

bitmask1

\n- V4 bitmask representing the set of attributes supported\n- on this filesystem\n-

server_ip

\n- IP address of server\n+

Synopsis

nfs.proc.commit

Values

version

\n+ NFS version\n

size

\n read bytes in this execution\n-

version

\n- NFS version\n+

bitmask0

\n+ V4 bitmask representing the set of attributes supported\n+ on this filesystem\n

offset

\n the file offset\n-

prot

\n- transfer protocol\n-

bitmask0

\n+

server_ip

\n+ IP address of server\n+

bitmask1

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n+

prot

\n+ transfer protocol\n

Description

\n All the nfs.proc.commit kernel functions were removed in kernel\n commit 200baa in December 2006, so these probes do not exist on Linux\n 2.6.21 and newer kernels.\n

\n \n Fires when client writes the buffered data to disk.\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-create.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-create.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::nfs.proc.create

probe::nfs.proc.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.create — \n NFS client creating file on server\n-

Synopsis

nfs.proc.create

Values

flag

\n- indicates create mode (only for NFSv3 and NFSv4)\n-

prot

\n- transfer protocol\n-

filename

\n- file name\n-

fh

\n- file handle of parent dir\n+

Synopsis

nfs.proc.create

Values

version

\n+ NFS version (the function is used for all NFS version)\n

filelen

\n length of file name\n+

filename

\n+ file name\n

server_ip

\n IP address of server\n-

version

\n- NFS version (the function is used for all NFS version)\n+

flag

\n+ indicates create mode (only for NFSv3 and NFSv4)\n+

fh

\n+ file handle of parent dir\n+

prot

\n+ transfer protocol\n

Prev Up Next
probe::nfs.proc.commit_setup Home probe::nfs.proc.handle_exception
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-lookup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-lookup.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.proc.lookup
probe::nfs.proc.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.lookup — \n NFS client opens/searches a file on server\n-

Synopsis

nfs.proc.lookup

Values

bitmask0

\n+

Synopsis

nfs.proc.lookup

Values

server_ip

\n+ IP address of server\n+

bitmask1

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n-

filename

\n- the name of file which client opens/searches on server\n-

server_ip

\n- IP address of server\n

prot

\n transfer protocol\n

name_len

\n the length of file name\n

version

\n NFS version\n-

bitmask1

\n+

filename

\n+ the name of file which client opens/searches on server\n+

bitmask0

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n

Prev Up Next
probe::nfs.proc.handle_exception Home probe::nfs.proc.open
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-open.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-open.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,17 +1,17 @@\n probe::nfs.proc.open
probe::nfs.proc.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.open — \n NFS client allocates file read/write context information\n

Synopsis

nfs.proc.open

Values

server_ip

\n IP address of server\n+

flag

\n+ file flag\n

mode

\n file mode\n+

prot

\n+ transfer protocol\n

version

\n NFS version (the function is used for all NFS version)\n

filename

\n file name\n-

prot

\n- transfer protocol\n-

flag

\n- file flag\n

Description

\n Allocate file read/write context information\n

Prev Up Next
probe::nfs.proc.lookup Home probe::nfs.proc.read
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-done.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-done.html", "unified_diff": "@@ -1,18 +1,18 @@\n probe::nfs.proc.read_done
probe::nfs.proc.read_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read_done — \n NFS client response to a read RPC task\n-

Synopsis

nfs.proc.read_done

Values

timestamp

\n- V4 timestamp, which is used for lease renewal\n+

Synopsis

nfs.proc.read_done

Values

version

\n+ NFS version\n

count

\n number of bytes read\n-

prot

\n- transfer protocol\n-

version

\n- NFS version\n

server_ip

\n IP address of server\n

status

\n result of last operation\n+

timestamp

\n+ V4 timestamp, which is used for lease renewal\n+

prot

\n+ transfer protocol\n

Description

\n Fires when a reply to a read RPC task is received or some read error occurs\n (timeout or socket shutdown).\n

Prev Up Next
probe::nfs.proc.read Home probe::nfs.proc.read_setup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-setup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-setup.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,18 +1,18 @@\n probe::nfs.proc.read_setup
probe::nfs.proc.read_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read_setup — \n NFS client setting up a read RPC task\n

Synopsis

nfs.proc.read_setup

Values

size

\n read bytes in this execution\n-

server_ip

\n- IP address of server\n

version

\n NFS version\n-

prot

\n- transfer protocol\n

count

\n read bytes in this execution\n

offset

\n the file offset \n+

server_ip

\n+ IP address of server\n+

prot

\n+ transfer protocol\n

Description

\n The read_setup function is used to setup a read RPC task.\n It is not doing the actual read operation.\n

Prev Up Next
probe::nfs.proc.read_done Home probe::nfs.proc.release
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfs.proc.read
probe::nfs.proc.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read — \n NFS client synchronously reads file from server\n

Synopsis

nfs.proc.read

Values

version

\n NFS version\n-

prot

\n- transfer protocol\n-

server_ip

\n- IP address of server\n-

offset

\n- the file offset\n-

flags

\n- used to set task->tk_flags in rpc_init_task function\n

count

\n read bytes in this execution\n+

flags

\n+ used to set task->tk_flags in rpc_init_task function\n+

offset

\n+ the file offset\n+

server_ip

\n+ IP address of server\n+

prot

\n+ transfer protocol\n

Description

\n All the nfs.proc.read kernel functions were removed in kernel commit\n 8e0969 in December 2006, so these probes do not exist on Linux\n 2.6.21 and newer kernels.\n

Prev Up Next
probe::nfs.proc.open Home probe::nfs.proc.read_done
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-release.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-release.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::nfs.proc.release
probe::nfs.proc.release
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.release — \n NFS client releases file read/write context information\n-

Synopsis

nfs.proc.release

Values

server_ip

\n- IP address of server\n-

mode

\n+

Synopsis

nfs.proc.release

Values

mode

\n file mode\n-

version

\n- NFS version (the function is used for all NFS version)\n+

server_ip

\n+ IP address of server\n

flag

\n file flag\n-

filename

\n- file name\n

prot

\n transfer protocol\n+

version

\n+ NFS version (the function is used for all NFS version)\n+

filename

\n+ file name\n

Description

\n Release file read/write context information\n

Prev Up Next
probe::nfs.proc.read_setup Home probe::nfs.proc.remove
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-remove.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-remove.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::nfs.proc.remove
probe::nfs.proc.remove
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.remove — \n NFS client removes a file on server\n-

Synopsis

nfs.proc.remove

Values

version

\n+

Synopsis

nfs.proc.remove

Values

filelen

\n+ length of file name\n+

version

\n NFS version (the function is used for all NFS version)\n+

filename

\n+ file name\n

server_ip

\n IP address of server\n-

filelen

\n- length of file name\n

fh

\n file handle of parent dir\n-

filename

\n- file name\n

prot

\n transfer protocol\n

Prev Up Next
probe::nfs.proc.release Home probe::nfs.proc.rename
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename-done.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename-done.html", "unified_diff": "@@ -1,20 +1,20 @@\n probe::nfs.proc.rename_done
probe::nfs.proc.rename_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.rename_done — \n NFS client response to a rename RPC task\n-

Synopsis

nfs.proc.rename_done

Values

prot

\n- transfer protocol\n-

new_fh

\n- file handle of new parent dir\n-

timestamp

\n- V4 timestamp, which is used for lease renewal\n-

version

\n+

Synopsis

nfs.proc.rename_done

Values

version

\n NFS version\n-

server_ip

\n- IP address of server\n-

status

\n- result of last operation\n

old_fh

\n file handle of old parent dir\n+

prot

\n+ transfer protocol\n+

status

\n+ result of last operation\n+

server_ip

\n+ IP address of server\n+

timestamp

\n+ V4 timestamp, which is used for lease renewal\n+

new_fh

\n+ file handle of new parent dir\n

Description

\n Fires when a reply to a rename RPC task is received or some rename\n error occurs (timeout or socket shutdown).\n

Prev Up Next
probe::nfs.proc.rename Home probe::nfs.proc.rename_setup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::nfs.proc.rename
probe::nfs.proc.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.rename — \n NFS client renames a file on server\n-

Synopsis

nfs.proc.rename

Values

old_name

\n- old file name\n-

new_fh

\n- file handle of new parent dir\n-

prot

\n- transfer protocol\n-

new_filelen

\n+

Synopsis

nfs.proc.rename

Values

new_filelen

\n length of new file name\n-

old_fh

\n- file handle of old parent dir\n-

old_filelen

\n- length of old file name\n

version

\n NFS version (the function is used for all NFS version)\n+

old_filelen

\n+ length of old file name\n

new_name

\n new file name\n+

prot

\n+ transfer protocol\n+

old_fh

\n+ file handle of old parent dir\n

server_ip

\n IP address of server\n+

new_fh

\n+ file handle of new parent dir\n+

old_name

\n+ old file name\n

Prev Up Next
probe::nfs.proc.remove Home probe::nfs.proc.rename_done
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-done.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-done.html", "unified_diff": "@@ -1,20 +1,20 @@\n probe::nfs.proc.write_done
probe::nfs.proc.write_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write_done — \n NFS client response to a write RPC task\n-

Synopsis

nfs.proc.write_done

Values

count

\n- number of bytes written\n-

timestamp

\n- V4 timestamp, which is used for lease renewal\n+

Synopsis

nfs.proc.write_done

Values

valid

\n+ fattr->valid, indicates which fields are valid \n

prot

\n transfer protocol\n-

valid

\n- fattr->valid, indicates which fields are valid \n

server_ip

\n IP address of server\n

status

\n result of last operation\n+

timestamp

\n+ V4 timestamp, which is used for lease renewal\n+

count

\n+ number of bytes written\n

version

\n NFS version\n

Description

\n Fires when a reply to a write RPC task is received or some write error occurs\n (timeout or socket shutdown).\n

Prev Up Next
probe::nfs.proc.write Home probe::nfs.proc.write_setup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-setup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-setup.html", "unified_diff": "@@ -1,28 +1,28 @@\n probe::nfs.proc.write_setup
probe::nfs.proc.write_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write_setup — \n NFS client setting up a write RPC task\n-

Synopsis

nfs.proc.write_setup

Values

count

\n+

Synopsis

nfs.proc.write_setup

Values

size

\n bytes written in this execution\n-

offset

\n- the file offset\n-

prot

\n- transfer protocol\n-

bitmask0

\n- V4 bitmask representing the set of attributes supported\n- on this filesystem\n+

version

\n+ NFS version\n

how

\n used to set args.stable. The stable value could be:\n NFS_UNSTABLE,NFS_DATA_SYNC,NFS_FILE_SYNC\n (in nfs.proc3.write_setup and nfs.proc4.write_setup)\n-

bitmask1

\n+

bitmask0

\n V4 bitmask representing the set of attributes supported\n- on this filesystem \n+ on this filesystem\n+

count

\n+ bytes written in this execution\n

server_ip

\n IP address of server\n-

size

\n- bytes written in this execution\n-

version

\n- NFS version\n+

offset

\n+ the file offset\n+

prot

\n+ transfer protocol\n+

bitmask1

\n+ V4 bitmask representing the set of attributes supported\n+ on this filesystem \n

Description

\n The write_setup function is used to setup a write RPC task.\n It is not doing the actual write operation.\n

Prev Up Next
probe::nfs.proc.write_done Home probe::nfsd.close
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::nfs.proc.write
probe::nfs.proc.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write — \n NFS client synchronously writes file to server\n-

Synopsis

nfs.proc.write

Values

offset

\n- the file offset\n-

bitmask0

\n+

Synopsis

nfs.proc.write

Values

prot

\n+ transfer protocol\n+

bitmask1

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n-

prot

\n- transfer protocol\n

flags

\n used to set task->tk_flags in rpc_init_task function\n-

bitmask1

\n+

offset

\n+ the file offset\n+

server_ip

\n+ IP address of server\n+

bitmask0

\n V4 bitmask representing the set of attributes supported\n on this filesystem\n-

version

\n- NFS version\n

size

\n read bytes in this execution\n-

server_ip

\n- IP address of server\n+

version

\n+ NFS version\n

Description

\n All the nfs.proc.write kernel functions were removed in kernel commit\n 200baa in December 2006, so these probes do not exist on Linux\n 2.6.21 and newer kernels.\n

Prev Up Next
probe::nfs.proc.rename_setup Home probe::nfs.proc.write_done
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-commit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-commit.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::nfsd.commit
probe::nfsd.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.commit — \n NFS server committing all pending writes to stable storage\n-

Synopsis

nfsd.commit

Values

size

\n- read bytes\n+

Synopsis

nfsd.commit

Values

flag

\n+ indicates whether this execution is a sync operation\n

count

\n read bytes\n-

client_ip

\n- the ip address of client\n

offset

\n the offset of file\n

fh

\n file handle (the first part is the length of the file handle)\n-

flag

\n- indicates whether this execution is a sync operation\n+

size

\n+ read bytes\n+

client_ip

\n+ the ip address of client\n

Prev Up Next
probe::nfsd.close Home probe::nfsd.create
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-create.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-create.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.create
probe::nfsd.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.create — \n NFS server creating a file(regular,dir,device,fifo) for client\n-

Synopsis

nfsd.create

Values

iap_mode

\n- file access mode\n-

filelen

\n- the length of file name\n+

Synopsis

nfsd.create

Values

type

\n+ file type(regular,dir,device,fifo ...)\n

filename

\n file name \n-

client_ip

\n- the ip address of client\n

iap_valid

\n Attribute flags\n

fh

\n file handle (the first part is the length of the file handle)\n-

type

\n- file type(regular,dir,device,fifo ...)\n+

client_ip

\n+ the ip address of client\n+

filelen

\n+ the length of file name\n+

iap_mode

\n+ file access mode\n

Description

\n Sometimes nfsd will call nfsd_create_v3 instead of this this probe point.\n

Prev Up Next
probe::nfsd.commit Home probe::nfsd.createv3
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-createv3.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-createv3.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::nfsd.createv3
probe::nfsd.createv3
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.createv3 — \n NFS server creating a regular file or set file attributes for client\n-

Synopsis

nfsd.createv3

Values

filelen

\n- the length of file name\n-

truncp

\n+

Synopsis

nfsd.createv3

Values

truncp

\n trunp arguments, indicates if the file shouldbe truncate\n+

iap_mode

\n+ file access mode\n+

filelen

\n+ the length of file name\n

filename

\n file name \n-

client_ip

\n- the ip address of client\n

iap_valid

\n Attribute flags\n

fh

\n file handle (the first part is the length of the file handle)\n-

createmode

\n- create mode .The possible values could be: NFS3_CREATE_EXCLUSIVE, NFS3_CREATE_UNCHECKED, or NFS3_CREATE_GUARDED\n

verifier

\n file attributes (atime,mtime,mode). It's used to reset file attributes for CREATE_EXCLUSIVE\n-

iap_mode

\n- file access mode\n+

client_ip

\n+ the ip address of client\n+

createmode

\n+ create mode .The possible values could be: NFS3_CREATE_EXCLUSIVE, NFS3_CREATE_UNCHECKED, or NFS3_CREATE_GUARDED\n

Description

\n This probepoints is only called by nfsd3_proc_create and\n nfsd4_open when op_claim_type is NFS4_OPEN_CLAIM_NULL.\n

Prev Up Next
probe::nfsd.create Home probe::nfsd.dispatch
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-dispatch.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-dispatch.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,15 +1,15 @@\n probe::nfsd.dispatch
probe::nfsd.dispatch
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.dispatch — \n NFS server receives an operation from client\n

Synopsis

nfsd.dispatch

Values

client_ip

\n the ip address of client\n-

version

\n- nfs version\n-

proc

\n- procedure number\n

xid

\n transmission id\n

proto

\n transfer protocol\n+

proc

\n+ procedure number\n

prog

\n program number\n+

version

\n+ nfs version\n

Prev Up Next
probe::nfsd.createv3 Home probe::nfsd.lookup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-lookup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-lookup.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::nfsd.lookup
probe::nfsd.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.lookup — \n NFS server opening or searching file for a file for client\n-

Synopsis

nfsd.lookup

Values

filelen

\n- the length of file name\n+

Synopsis

nfsd.lookup

Values

fh

\n+ file handle of parent dir(the first part is the length of the file handle)\n

filename

\n file name \n

client_ip

\n the ip address of client\n-

fh

\n- file handle of parent dir(the first part is the length of the file handle)\n+

filelen

\n+ the length of file name\n

Prev Up Next
probe::nfsd.dispatch Home probe::nfsd.open
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-open.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-open.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::nfsd.open
probe::nfsd.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.open — \n NFS server opening a file for client\n-

Synopsis

nfsd.open

Values

access

\n- indicates the type of open (read/write/commit/readdir...) \n+

Synopsis

nfsd.open

Values

type

\n+ type of file (regular file or dir)\n

fh

\n file handle (the first part is the length of the file handle)\n-

type

\n- type of file (regular file or dir)\n+

access

\n+ indicates the type of open (read/write/commit/readdir...) \n

client_ip

\n the ip address of client\n

Prev Up Next
probe::nfsd.lookup Home probe::nfsd.proc.commit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-commit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-commit.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::nfsd.proc.commit
probe::nfsd.proc.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.commit — \n NFS server performing a commit operation for client\n-

Synopsis

nfsd.proc.commit

Values

proto

\n- transfer protocol\n+

Synopsis

nfsd.proc.commit

Values

offset

\n+ the offset of file \n

version

\n nfs version\n-

uid

\n- requester's user id\n-

gid

\n- requester's group id\n-

fh

\n- file handle (the first part is the length of the file handle)\n-

offset

\n- the offset of file \n-

size

\n- read bytes\n

count

\n read bytes\n+

fh

\n+ file handle (the first part is the length of the file handle)\n+

proto

\n+ transfer protocol\n

client_ip

\n the ip address of client\n+

gid

\n+ requester's group id\n+

size

\n+ read bytes\n+

uid

\n+ requester's user id\n

Prev Up Next
probe::nfsd.open Home probe::nfsd.proc.create
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-create.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-create.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.proc.create
probe::nfsd.proc.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.create — \n NFS server creating a file for client\n-

Synopsis

nfsd.proc.create

Values

version

\n- nfs version\n-

uid

\n+

Synopsis

nfsd.proc.create

Values

uid

\n requester's user id\n-

proto

\n- transfer protocol\n

filelen

\n length of file name\n-

client_ip

\n- the ip address of client\n+

version

\n+ nfs version\n

filename

\n file name\n-

gid

\n- requester's group id\n

fh

\n file handle (the first part is the length of the file handle)\n+

proto

\n+ transfer protocol\n+

gid

\n+ requester's group id\n+

client_ip

\n+ the ip address of client\n

Prev Up Next
probe::nfsd.proc.commit Home probe::nfsd.proc.lookup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-lookup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-lookup.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.proc.lookup
probe::nfsd.proc.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.lookup — \n NFS server opening or searching for a file for client\n-

Synopsis

nfsd.proc.lookup

Values

filelen

\n- the length of file name\n+

Synopsis

nfsd.proc.lookup

Values

uid

\n+ requester's user id\n

version

\n nfs version\n-

uid

\n- requester's user id\n

filename

\n file name \n-

client_ip

\n- the ip address of client\n+

fh

\n+ file handle of parent dir (the first part is the length of the file handle)\n

proto

\n transfer protocol\n+

filelen

\n+ the length of file name\n

gid

\n requester's group id\n-

fh

\n- file handle of parent dir (the first part is the length of the file handle)\n+

client_ip

\n+ the ip address of client\n

Prev Up Next
probe::nfsd.proc.create Home probe::nfsd.proc.read
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-read.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::nfsd.proc.read
probe::nfsd.proc.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.read — \n NFS server reading file for client\n-

Synopsis

nfsd.proc.read

Values

uid

\n+

Synopsis

nfsd.proc.read

Values

vec

\n+ struct kvec, includes buf address in kernel address and length of each buffer\n+

uid

\n requester's user id\n-

size

\n- read bytes\n-

count

\n- read bytes\n+

proto

\n+ transfer protocol\n+

gid

\n+ requester's group id\n

client_ip

\n the ip address of client\n-

vec

\n- struct kvec, includes buf address in kernel address and length of each buffer\n-

version

\n- nfs version\n+

size

\n+ read bytes\n

vlen

\n read blocks \n

offset

\n the offset of file \n+

version

\n+ nfs version\n+

count

\n+ read bytes\n

fh

\n file handle (the first part is the length of the file handle)\n-

proto

\n- transfer protocol\n-

gid

\n- requester's group id\n

Prev Up Next
probe::nfsd.proc.lookup Home probe::nfsd.proc.remove
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-remove.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-remove.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.proc.remove
probe::nfsd.proc.remove
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.remove — \n NFS server removing a file for client\n-

Synopsis

nfsd.proc.remove

Values

proto

\n- transfer protocol\n-

version

\n+

Synopsis

nfsd.proc.remove

Values

version

\n nfs version\n-

uid

\n- requester's user id\n-

gid

\n- requester's group id\n

fh

\n file handle (the first part is the length of the file handle)\n-

filelen

\n- length of file name\n-

client_ip

\n- the ip address of client\n

filename

\n file name\n+

proto

\n+ transfer protocol\n+

gid

\n+ requester's group id\n+

client_ip

\n+ the ip address of client\n+

uid

\n+ requester's user id\n+

filelen

\n+ length of file name\n

Prev Up Next
probe::nfsd.proc.read Home probe::nfsd.proc.rename
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-rename.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-rename.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::nfsd.proc.rename
probe::nfsd.proc.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.rename — \n NFS Server renaming a file for client\n-

Synopsis

nfsd.proc.rename

Values

gid

\n- requester's group id\n+

Synopsis

nfsd.proc.rename

Values

tlen

\n+ length of new file name\n

tfh

\n file handler of new path\n-

fh

\n- file handler of old path\n-

flen

\n- length of old file name \n-

tlen

\n- length of new file name\n+

uid

\n+ requester's user id\n

client_ip

\n the ip address of client\n-

filename

\n- old file name \n+

gid

\n+ requester's group id\n

tname

\n new file name\n-

uid

\n- requester's user id\n+

filename

\n+ old file name \n+

fh

\n+ file handler of old path\n+

flen

\n+ length of old file name \n

Prev Up Next
probe::nfsd.proc.remove Home probe::nfsd.proc.write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-write.html", "unified_diff": "@@ -1,27 +1,27 @@\n probe::nfsd.proc.write
probe::nfsd.proc.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.write — \n NFS server writing data to file for client\n-

Synopsis

nfsd.proc.write

Values

gid

\n- requester's group id\n-

fh

\n- file handle (the first part is the length of the file handle)\n-

vec

\n- struct kvec, includes buf address in kernel address and length of each buffer\n-

offset

\n- the offset of file \n-

stable

\n- argp->stable\n-

size

\n- read bytes\n-

count

\n+

Synopsis

nfsd.proc.write

Values

size

\n read bytes\n

client_ip

\n the ip address of client\n+

gid

\n+ requester's group id\n

proto

\n transfer protocol\n-

version

\n- nfs version\n+

fh

\n+ file handle (the first part is the length of the file handle)\n+

count

\n+ read bytes\n

vlen

\n read blocks \n+

version

\n+ nfs version\n+

offset

\n+ the offset of file \n+

vec

\n+ struct kvec, includes buf address in kernel address and length of each buffer\n+

stable

\n+ argp->stable\n

uid

\n requester's user id\n

Prev Up Next
probe::nfsd.proc.rename Home probe::nfsd.read
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-read.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.read
probe::nfsd.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.read — \n NFS server reading data from a file for client\n-

Synopsis

nfsd.read

Values

vlen

\n- read blocks \n-

vec

\n+

Synopsis

nfsd.read

Values

vec

\n struct kvec, includes buf address in kernel address and length of each buffer\n-

offset

\n- the offset of file \n-

file

\n- argument file, indicates if the file has been opened.\n-

size

\n- read bytes\n-

count

\n- read bytes\n

client_ip

\n the ip address of client\n+

size

\n+ read bytes\n

fh

\n file handle (the first part is the length of the file handle)\n+

file

\n+ argument file, indicates if the file has been opened.\n+

vlen

\n+ read blocks \n+

offset

\n+ the offset of file \n+

count

\n+ read bytes\n

Prev Up Next
probe::nfsd.proc.write Home probe::nfsd.rename
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-rename.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-rename.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::nfsd.rename
probe::nfsd.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.rename — \n NFS server renaming a file for client\n-

Synopsis

nfsd.rename

Values

tname

\n+

Synopsis

nfsd.rename

Values

flen

\n+ length of old file name \n+

fh

\n+ file handler of old path\n+

filename

\n+ old file name \n+

tname

\n new file name\n+

client_ip

\n+ the ip address of client\n

tfh

\n file handler of new path\n-

fh

\n- file handler of old path\n-

flen

\n- length of old file name \n

tlen

\n length of new file name\n-

client_ip

\n- the ip address of client\n-

filename

\n- old file name \n

Prev Up Next
probe::nfsd.read Home probe::nfsd.unlink
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-unlink.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-unlink.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::nfsd.unlink
probe::nfsd.unlink
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.unlink — \n NFS server removing a file or a directory for client\n-

Synopsis

nfsd.unlink

Values

filelen

\n- the length of file name\n-

client_ip

\n- the ip address of client\n+

Synopsis

nfsd.unlink

Values

fh

\n+ file handle (the first part is the length of the file handle)\n

filename

\n file name \n-

fh

\n- file handle (the first part is the length of the file handle)\n

type

\n file type (file or dir)\n+

client_ip

\n+ the ip address of client\n+

filelen

\n+ the length of file name\n

Prev Up Next
probe::nfsd.rename Home probe::nfsd.write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-nfsd-write.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::nfsd.write
probe::nfsd.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.write — \n NFS server writing data to a file for client\n-

Synopsis

nfsd.write

Values

fh

\n- file handle (the first part is the length of the file handle)\n-

size

\n- read bytes\n-

client_ip

\n- the ip address of client\n-

count

\n- read bytes\n-

vec

\n+

Synopsis

nfsd.write

Values

vec

\n struct kvec, includes buf address in kernel address and length of each buffer\n-

offset

\n- the offset of file \n

file

\n argument file, indicates if the file has been opened.\n+

fh

\n+ file handle (the first part is the length of the file handle)\n+

offset

\n+ the offset of file \n

vlen

\n read blocks \n+

count

\n+ read bytes\n+

client_ip

\n+ the ip address of client\n+

size

\n+ read bytes\n

Prev Up Next
probe::nfsd.unlink Home Chapter 32. Speculation
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-off.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-off.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::scheduler.cpu_off
probe::scheduler.cpu_off
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.cpu_off — \n Process is about to stop running on a cpu\n-

Synopsis

scheduler.cpu_off

Values

task_next

\n- the process replacing current\n-

idle

\n- boolean indicating whether current is the idle process\n+

Synopsis

scheduler.cpu_off

Values

task_prev

\n+ the process leaving the cpu (same as current)\n

name

\n name of the probe point\n-

task_prev

\n- the process leaving the cpu (same as current)\n+

idle

\n+ boolean indicating whether current is the idle process\n+

task_next

\n+ the process replacing current\n

Context

\n The process leaving the cpu.\n

Prev Up Next
probe::scheduler.balance Home probe::scheduler.cpu_on
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-on.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-on.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::scheduler.cpu_on
probe::scheduler.cpu_on
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.cpu_on — \n Process is beginning execution on a cpu\n-

Synopsis

scheduler.cpu_on

Values

task_prev

\n- the process that was previously running on this cpu\n+

Synopsis

scheduler.cpu_on

Values

name

\n+ name of the probe point\n

idle

\n - boolean indicating whether current is the idle process\n-

name

\n- name of the probe point\n+

task_prev

\n+ the process that was previously running on this cpu\n

Context

\n The resuming process.\n

Prev Up Next
probe::scheduler.cpu_off Home probe::scheduler.ctxswitch
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-ctxswitch.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-ctxswitch.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::scheduler.ctxswitch
probe::scheduler.ctxswitch
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.ctxswitch — \n A context switch is occuring.\n-

Synopsis

scheduler.ctxswitch

Values

next_pid

\n- The PID of the process to be switched in\n-

prev_tid

\n- The TID of the process to be switched out\n-

next_tid

\n+

Synopsis

scheduler.ctxswitch

Values

next_tid

\n The TID of the process to be switched in\t \n-

prev_pid

\n- The PID of the process to be switched out\n-

nexttsk_state

\n- the state of the process to be switched in\n-

next_priority

\n- The priority of the process to be switched in\n

next_task_name

\n The name of the process to be switched in\n-

name

\n- name of the probe point\n+

nexttsk_state

\n+ the state of the process to be switched in\n+

prev_tid

\n+ The TID of the process to be switched out\n

prevtsk_state

\n the state of the process to be switched out\n-

prev_priority

\n- The priority of the process to be switched out\n

prev_task_name

\n The name of the process to be switched out\n+

name

\n+ name of the probe point\n+

prev_priority

\n+ The priority of the process to be switched out\n+

prev_pid

\n+ The PID of the process to be switched out\n+

next_pid

\n+ The PID of the process to be switched in\n+

next_priority

\n+ The priority of the process to be switched in\n

Prev Up Next
probe::scheduler.cpu_on Home probe::scheduler.kthread_stop
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-kthread-stop-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-kthread-stop-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::scheduler.kthread_stop.return
probe::scheduler.kthread_stop.return
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.kthread_stop.return — \n A kthread is stopped and gets the return value\n-

Synopsis

scheduler.kthread_stop.return

Values

name

\n- name of the probe point\n-

return_value

\n+

Synopsis

scheduler.kthread_stop.return

Values

return_value

\n return value after stopping the thread\n+

name

\n+ name of the probe point\n

Prev Up Next
probe::scheduler.kthread_stop Home probe::scheduler.migrate
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-kthread-stop.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-kthread-stop.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::scheduler.kthread_stop
probe::scheduler.kthread_stop
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.kthread_stop — \n A thread created by kthread_create is being stopped\n-

Synopsis

scheduler.kthread_stop

Values

thread_pid

\n- PID of the thread being stopped\n-

thread_priority

\n+

Synopsis

scheduler.kthread_stop

Values

thread_priority

\n priority of the thread\n+

thread_pid

\n+ PID of the thread being stopped\n

Prev Up Next
probe::scheduler.ctxswitch Home probe::scheduler.kthread_stop.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-migrate.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-migrate.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::scheduler.migrate
probe::scheduler.migrate
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.migrate — \n Task migrating across cpus\n-

Synopsis

scheduler.migrate

Values

pid

\n- PID of the task being migrated\n-

cpu_from

\n- the original cpu\n+

Synopsis

scheduler.migrate

Values

priority

\n+ priority of the task being migrated\n

name

\n name of the probe point\n-

task

\n- the process that is being migrated\n-

priority

\n- priority of the task being migrated\n+

cpu_from

\n+ the original cpu\n+

pid

\n+ PID of the task being migrated\n

cpu_to

\n the destination cpu\n+

task

\n+ the process that is being migrated\n

Prev Up Next
probe::scheduler.kthread_stop.return Home probe::scheduler.process_exit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-exit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-exit.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::scheduler.process_exit
probe::scheduler.process_exit
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_exit — \n Process exiting\n-

Synopsis

scheduler.process_exit

Values

pid

\n- PID of the process exiting\n-

priority

\n+

Synopsis

scheduler.process_exit

Values

priority

\n priority of the process exiting\n+

pid

\n+ PID of the process exiting\n

name

\n name of the probe point\n

Prev Up Next
probe::scheduler.migrate Home probe::scheduler.process_fork
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-fork.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-fork.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,9 +1,9 @@\n probe::scheduler.process_fork
probe::scheduler.process_fork
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_fork — \n Process forked\n

Synopsis

scheduler.process_fork

Values

parent_pid

\n PID of the parent process\n-

name

\n- name of the probe point\n

child_pid

\n PID of the child process\n+

name

\n+ name of the probe point\n

Prev Up Next
probe::scheduler.process_exit Home probe::scheduler.process_free
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-free.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-free.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,9 +1,9 @@\n probe::scheduler.process_free
probe::scheduler.process_free
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_free — \n Scheduler freeing a data structure for a process\n

Synopsis

scheduler.process_free

Values

pid

\n PID of the process getting freed\n-

priority

\n- priority of the process getting freed\n

name

\n name of the probe point\n+

priority

\n+ priority of the process getting freed\n

Prev Up Next
probe::scheduler.process_fork Home probe::scheduler.process_wait
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-wait.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-wait.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::scheduler.process_wait
probe::scheduler.process_wait
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_wait — \n Scheduler starting to wait on a process\n-

Synopsis

scheduler.process_wait

Values

name

\n- name of the probe point\n-

pid

\n+

Synopsis

scheduler.process_wait

Values

pid

\n PID of the process scheduler is waiting on\n+

name

\n+ name of the probe point\n

Prev Up Next
probe::scheduler.process_free Home probe::scheduler.signal_send
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-signal-send.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-signal-send.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,9 +1,9 @@\n probe::scheduler.signal_send
probe::scheduler.signal_send
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.signal_send — \n Sending a signal\n

Synopsis

scheduler.signal_send

Values

signal_number

\n signal number\n-

name

\n- name of the probe point\n

pid

\n pid of the process sending signal\n+

name

\n+ name of the probe point\n

Prev Up Next
probe::scheduler.process_wait Home probe::scheduler.tick
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wait-task.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wait-task.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::scheduler.wait_task
probe::scheduler.wait_task
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wait_task — \n Waiting on a task to unschedule (become inactive)\n-

Synopsis

scheduler.wait_task

Values

task_priority

\n- priority of the task\n-

name

\n+

Synopsis

scheduler.wait_task

Values

name

\n name of the probe point\n+

task_priority

\n+ priority of the task\n

task_pid

\n PID of the task the scheduler is waiting on\n

Prev Up Next
probe::scheduler.tick Home probe::scheduler.wakeup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup-new.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup-new.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::scheduler.wakeup_new
probe::scheduler.wakeup_new
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wakeup_new — \n Newly created task is woken up for the first time\n-

Synopsis

scheduler.wakeup_new

Values

task_priority

\n+

Synopsis

scheduler.wakeup_new

Values

task_cpu

\n+ cpu of the task woken up\n+

task_priority

\n priority of the new task\n-

task_state

\n- state of the task woken up\n-

name

\n- name of the probe point\n

task_pid

\n PID of the new task woken up\n+

task_state

\n+ state of the task woken up\n

task_tid

\n TID of the new task woken up\n-

task_cpu

\n- cpu of the task woken up\n+

name

\n+ name of the probe point\n

Prev Up Next
probe::scheduler.wakeup Home Chapter 9. IO Scheduler and block IO Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::scheduler.wakeup
probe::scheduler.wakeup
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wakeup — \n Task is woken up\n-

Synopsis

scheduler.wakeup

Values

task_cpu

\n- cpu of the task being woken up\n-

task_tid

\n+

Synopsis

scheduler.wakeup

Values

task_tid

\n tid of the task being woken up\n-

task_pid

\n- PID of the task being woken up\n

name

\n name of the probe point\n

task_state

\n state of the task being woken up\n+

task_cpu

\n+ cpu of the task being woken up\n

task_priority

\n priority of the task being woken up\n+

task_pid

\n+ PID of the task being woken up\n

Prev Up Next
probe::scheduler.wait_task Home probe::scheduler.wakeup_new
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iocompleted.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iocompleted.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::scsi.iocompleted
probe::scsi.iocompleted
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iocompleted — \n SCSI mid-layer running the completion processing for block device I/O requests\n-

Synopsis

scsi.iocompleted

Values

device_state_str

\n- The current state of the device, as a string\n-

channel

\n- The channel number\n-

req_addr

\n+

Synopsis

scsi.iocompleted

Values

req_addr

\n The current struct request pointer, as a number\n-

goodbytes

\n- The bytes completed\n-

host_no

\n- The host number\n

data_direction_str

\n Data direction, as a string\n-

lun

\n- The lun number\n+

device_state_str

\n+ The current state of the device, as a string\n

dev_id

\n The scsi device id\n+

goodbytes

\n+ The bytes completed\n+

lun

\n+ The lun number\n+

channel

\n+ The channel number\n

device_state

\n The current state of the device\n+

host_no

\n+ The host number\n

data_direction

\n The data_direction specifies whether this command is from/to\n the device\n

Prev Up Next
Chapter 10. SCSI Tapset Home probe::scsi.iodispatching
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodispatching.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodispatching.html", "unified_diff": "@@ -1,27 +1,27 @@\n probe::scsi.iodispatching
probe::scsi.iodispatching
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iodispatching — \n SCSI mid-layer dispatched low-level SCSI command\n-

Synopsis

scsi.iodispatching

Values

device_state

\n- The current state of the device\n+

Synopsis

scsi.iodispatching

Values

host_no

\n+ The host number\n

data_direction

\n The data_direction specifies whether this command is from/to the device\n 0 (DMA_BIDIRECTIONAL), 1 (DMA_TO_DEVICE),\n 2 (DMA_FROM_DEVICE), 3 (DMA_NONE)\n-

data_direction_str

\n- Data direction, as a string\n-

request_buffer

\n- The request buffer address\n-

dev_id

\n- The scsi device id\n+

device_state

\n+ The current state of the device\n

lun

\n The lun number\n-

req_addr

\n- The current struct request pointer, as a number\n-

host_no

\n- The host number\n-

request_bufflen

\n- The request buffer length\n

channel

\n The channel number\n+

dev_id

\n+ The scsi device id\n+

request_bufflen

\n+ The request buffer length\n

device_state_str

\n The current state of the device, as a string\n+

request_buffer

\n+ The request buffer address\n+

data_direction_str

\n+ Data direction, as a string\n+

req_addr

\n+ The current struct request pointer, as a number\n

Prev Up Next
probe::scsi.iocompleted Home probe::scsi.iodone
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodone.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodone.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::scsi.iodone
probe::scsi.iodone
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iodone — \n SCSI command completed by low level driver and enqueued into the done queue.\n-

Synopsis

scsi.iodone

Values

data_direction

\n- The data_direction specifies whether this command is\n- from/to the device.\n+

Synopsis

scsi.iodone

Values

scsi_timer_pending

\n+ 1 if a timer is pending on this request\n

device_state

\n The current state of the device\n+

data_direction

\n+ The data_direction specifies whether this command is\n+ from/to the device.\n+

host_no

\n+ The host number\n

dev_id

\n The scsi device id\n

lun

\n The lun number\n+

channel

\n+ The channel number\n

data_direction_str

\n Data direction, as a string\n-

host_no

\n- The host number\n-

req_addr

\n- The current struct request pointer, as a number\n

device_state_str

\n The current state of the device, as a string\n-

channel

\n- The channel number\n-

scsi_timer_pending

\n- 1 if a timer is pending on this request\n+

req_addr

\n+ The current struct request pointer, as a number\n

Prev Up Next
probe::scsi.iodispatching Home probe::scsi.ioentry
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioentry.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioentry.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,13 +1,13 @@\n probe::scsi.ioentry
probe::scsi.ioentry
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.ioentry — \n Prepares a SCSI mid-layer request\n

Synopsis

scsi.ioentry

Values

device_state_str

\n The current state of the device, as a string\n-

req_addr

\n- The current struct request pointer, as a number\n-

disk_major

\n- The major number of the disk (-1 if no information)\n-

disk_minor

\n- The minor number of the disk (-1 if no information)\n

device_state

\n The current state of the device\n+

disk_minor

\n+ The minor number of the disk (-1 if no information)\n+

disk_major

\n+ The major number of the disk (-1 if no information)\n+

req_addr

\n+ The current struct request pointer, as a number\n

Prev Up Next
probe::scsi.iodone Home probe::scsi.ioexecute
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioexecute.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioexecute.html", "unified_diff": "@@ -1,28 +1,28 @@\n probe::scsi.ioexecute
probe::scsi.ioexecute
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.ioexecute — \n Create mid-layer SCSI request and wait for the result\n-

Synopsis

scsi.ioexecute

Values

request_bufflen

\n+

Synopsis

scsi.ioexecute

Values

retries

\n+ Number of times to retry request\n+

request_bufflen

\n The data buffer buffer length\n

device_state_str

\n The current state of the device, as a string\n+

request_buffer

\n+ The data buffer address\n

data_direction_str

\n Data direction, as a string\n

lun

\n The lun number\n-

device_state

\n- The current state of the device\n+

dev_id

\n+ The scsi device id\n

data_direction

\n The data_direction specifies whether this command is\n from/to the device.\n-

retries

\n- Number of times to retry request\n+

timeout

\n+ Request timeout in seconds\n

channel

\n The channel number\n

host_no

\n The host number\n-

timeout

\n- Request timeout in seconds\n-

request_buffer

\n- The data buffer address\n-

dev_id

\n- The scsi device id\n+

device_state

\n+ The current state of the device\n

Prev Up Next
probe::scsi.ioentry Home probe::scsi.set_state
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-set-state.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-scsi-set-state.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,19 +1,19 @@\n probe::scsi.set_state
probe::scsi.set_state
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.set_state — \n Order SCSI device state change\n

Synopsis

scsi.set_state

Values

channel

\n The channel number\n+

old_state_str

\n+ The current state of the device, as a string\n

host_no

\n The host number\n-

old_state

\n- The current state of the device\n-

dev_id

\n- The scsi device id\n

state

\n The new state of the device\n+

old_state

\n+ The current state of the device\n

state_str

\n The new state of the device, as a string\n

lun

\n The lun number\n-

old_state_str

\n- The current state of the device, as a string\n+

dev_id

\n+ The scsi device id\n

Prev Up Next
probe::scsi.ioexecute Home Chapter 11. TTY Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-check-ignored.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-check-ignored.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::signal.check_ignored
probe::signal.check_ignored
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.check_ignored — \n Checking to see signal is ignored\n-

Synopsis

signal.check_ignored

Values

pid_name

\n- Name of the process receiving the signal\n-

sig_name

\n+

Synopsis

signal.check_ignored

Values

sig_name

\n A string representation of the signal\n-

sig_pid

\n- The PID of the process receiving the signal\n

sig

\n The number of the signal\n+

pid_name

\n+ Name of the process receiving the signal\n+

sig_pid

\n+ The PID of the process receiving the signal\n

Prev Up Next
function::sigset_mask_str Home probe::signal.check_ignored.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-checkperm.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-checkperm.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::signal.checkperm
probe::signal.checkperm
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.checkperm — \n Check being performed on a sent signal\n-

Synopsis

signal.checkperm

Values

pid_name

\n- Name of the process receiving the signal\n-

task

\n- A task handle to the signal recipient\n-

sig_name

\n- A string representation of the signal\n-

sig_pid

\n- The PID of the process receiving the signal\n+

Synopsis

signal.checkperm

Values

si_code

\n+ Indicates the signal type\n

name

\n Name of the probe point\n+

sig_pid

\n+ The PID of the process receiving the signal\n

sinfo

\n The address of the siginfo structure\n+

sig_name

\n+ A string representation of the signal\n+

pid_name

\n+ Name of the process receiving the signal\n

sig

\n The number of the signal\n-

si_code

\n- Indicates the signal type\n+

task

\n+ A task handle to the signal recipient\n

Prev Up Next
probe::signal.check_ignored.return Home probe::signal.checkperm.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-do-action-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-do-action-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.do_action.return
probe::signal.do_action.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.do_action.return — \n Examining or changing a signal action completed\n-

Synopsis

signal.do_action.return

Values

name

\n- Name of the probe point\n-

retstr

\n+

Synopsis

signal.do_action.return

Values

retstr

\n Return value as a string\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.do_action Home probe::signal.flush
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-do-action.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-do-action.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::signal.do_action
probe::signal.do_action
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.do_action — \n Examining or changing a signal action\n-

Synopsis

signal.do_action

Values

sig

\n- The signal to be examined/changed\n-

name

\n+

Synopsis

signal.do_action

Values

name

\n Name of the probe point\n+

sa_handler

\n+ The new handler of the signal\n+

sa_mask

\n+ The new mask of the signal\n+

sig

\n+ The signal to be examined/changed\n+

sig_name

\n+ A string representation of the signal\n

sigact_addr

\n The address of the new sigaction\n struct associated with the signal\n

oldsigact_addr

\n The address of the old sigaction\n struct associated with the signal\n-

sig_name

\n- A string representation of the signal\n-

sa_mask

\n- The new mask of the signal\n-

sa_handler

\n- The new handler of the signal\n

Prev Up Next
probe::signal.checkperm.return Home probe::signal.do_action.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-flush.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-flush.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::signal.flush
probe::signal.flush
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.flush — \n Flushing all pending signals for a task\n-

Synopsis

signal.flush

Values

sig_pid

\n- The PID of the process associated with the task\n- performing the flush\n-

name

\n- Name of the probe point\n-

pid_name

\n+

Synopsis

signal.flush

Values

pid_name

\n The name of the process associated with the task\n performing the flush\n

task

\n The task handler of the process performing the flush\n+

sig_pid

\n+ The PID of the process associated with the task\n+ performing the flush\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.do_action.return Home probe::signal.force_segv
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-force-segv.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-force-segv.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::signal.force_segv
probe::signal.force_segv
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.force_segv — \n Forcing send of SIGSEGV\n-

Synopsis

signal.force_segv

Values

sig_pid

\n- The PID of the process receiving the signal\n-

name

\n- Name of the probe point\n-

sig_name

\n- A string representation of the signal\n+

Synopsis

signal.force_segv

Values

pid_name

\n+ Name of the process receiving the signal\n

sig

\n The number of the signal\n-

pid_name

\n- Name of the process receiving the signal\n+

sig_name

\n+ A string representation of the signal\n+

name

\n+ Name of the probe point\n+

sig_pid

\n+ The PID of the process receiving the signal\n

Prev Up Next
probe::signal.flush Home probe::signal.force_segv.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-handle.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-handle.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::signal.handle
probe::signal.handle
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.handle — \n Signal handler being invoked\n-

Synopsis

signal.handle

Values

name

\n- Name of the probe point\n-

sinfo

\n- The address of the siginfo table\n+

Synopsis

signal.handle

Values

sig

\n+ The signal number that invoked the signal handler\n

sig_name

\n A string representation of the signal\n-

sig_mode

\n- Indicates whether the signal was a user-mode or kernel-mode signal\n-

ka_addr

\n- The address of the k_sigaction table\n- associated with the signal\n-

sig

\n- The signal number that invoked the signal handler\n+

sinfo

\n+ The address of the siginfo table\n+

sig_code

\n+ The si_code value of the siginfo signal\n+

name

\n+ Name of the probe point\n

regs

\n The address of the kernel-mode stack area (deprecated in\n SystemTap 2.1)\n

oldset_addr

\n The address of the bitmask array of blocked signals\n (deprecated in SystemTap 2.1)\n-

sig_code

\n- The si_code value of the siginfo signal\n+

ka_addr

\n+ The address of the k_sigaction table\n+ associated with the signal\n+

sig_mode

\n+ Indicates whether the signal was a user-mode or kernel-mode signal\n

Prev Up Next
probe::signal.force_segv.return Home probe::signal.handle.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-pending-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-pending-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.pending.return
probe::signal.pending.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.pending.return — \n Examination of pending signal completed\n-

Synopsis

signal.pending.return

Values

name

\n- Name of the probe point\n-

retstr

\n+

Synopsis

signal.pending.return

Values

retstr

\n Return value as a string\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.pending Home probe::signal.procmask
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-pending.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-pending.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,14 +1,14 @@\n probe::signal.pending
probe::signal.pending
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.pending — \n Examining pending signal\n

Synopsis

signal.pending

Values

sigset_add

\n The address of the user-space signal set\n (sigset_t)\n-

sigset_size

\n- The size of the user-space signal set\n

name

\n Name of the probe point\n+

sigset_size

\n+ The size of the user-space signal set\n

Description

\n This probe is used to examine a set of signals pending for delivery\n to a specific thread. This normally occurs when the\n do_sigpending kernel function is executed.\n

Prev Up Next
probe::signal.handle.return Home probe::signal.pending.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.procmask.return
probe::signal.procmask.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.procmask.return — \n Examining or changing blocked signals completed\n-

Synopsis

signal.procmask.return

Values

retstr

\n- Return value as a string\n-

name

\n+

Synopsis

signal.procmask.return

Values

name

\n Name of the probe point\n+

retstr

\n+ Return value as a string\n

Prev Up Next
probe::signal.procmask Home probe::signal.send
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::signal.procmask
probe::signal.procmask
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.procmask — \n Examining or changing blocked signals\n-

Synopsis

signal.procmask

Values

name

\n- Name of the probe point\n-

oldsigset_addr

\n+

Synopsis

signal.procmask

Values

oldsigset_addr

\n The old address of the signal set\n (sigset_t)\n+

name

\n+ Name of the probe point\n+

how

\n+ Indicates how to change the blocked signals; possible values are\n+ SIG_BLOCK=0 (for blocking signals),\n+ SIG_UNBLOCK=1 (for unblocking signals), and\n+ SIG_SETMASK=2 for setting the signal mask.\n

sigset

\n The actual value to be set for sigset_t\n (correct?)\n

sigset_addr

\n The address of the signal set (sigset_t)\n to be implemented\n-

how

\n- Indicates how to change the blocked signals; possible values are\n- SIG_BLOCK=0 (for blocking signals),\n- SIG_UNBLOCK=1 (for unblocking signals), and\n- SIG_SETMASK=2 for setting the signal mask.\n

Prev Up Next
probe::signal.pending.return Home probe::signal.procmask.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-return.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,17 +1,17 @@\n probe::signal.send.return
probe::signal.send.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send.return — \n Signal being sent to a process completed (deprecated in SystemTap 2.1)\n

Synopsis

signal.send.return

Values

shared

\n Indicates whether the sent signal is shared by the thread group.\n-

send2queue

\n- Indicates whether the sent signal was sent to an existing sigqueue\n-

retstr

\n- The return value to either __group_send_sig_info, specific_send_sig_info, or send_sigqueue\n

name

\n The name of the function used to send out the signal\n+

retstr

\n+ The return value to either __group_send_sig_info, specific_send_sig_info, or send_sigqueue\n+

send2queue

\n+ Indicates whether the sent signal was sent to an existing sigqueue\n

Context

\n The signal's sender. (correct?)\n

Description

\n Possible __group_send_sig_info and\n specific_send_sig_info return values are as follows;\n

\n \n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-sig-queue-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-sig-queue-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.send_sig_queue.return

probe::signal.send_sig_queue.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send_sig_queue.return — \n Queuing a signal to a process completed\n-

Synopsis

signal.send_sig_queue.return

Values

name

\n- Name of the probe point\n-

retstr

\n+

Synopsis

signal.send_sig_queue.return

Values

retstr

\n Return value as a string\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.send_sig_queue Home probe::signal.sys_tgkill
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-sig-queue.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send-sig-queue.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::signal.send_sig_queue
probe::signal.send_sig_queue
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send_sig_queue — \n Queuing a signal to a process\n-

Synopsis

signal.send_sig_queue

Values

pid_name

\n- Name of the process to which the signal is queued\n-

sig_pid

\n- The PID of the process to which the signal is queued\n+

Synopsis

signal.send_sig_queue

Values

sigqueue_addr

\n+ The address of the signal queue\n

name

\n Name of the probe point\n-

sig_name

\n- A string representation of the signal\n-

sigqueue_addr

\n- The address of the signal queue\n+

sig_pid

\n+ The PID of the process to which the signal is queued\n

sig

\n The queued signal\n+

pid_name

\n+ Name of the process to which the signal is queued\n+

sig_name

\n+ A string representation of the signal\n

Prev Up Next
probe::signal.send.return Home probe::signal.send_sig_queue.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-send.html", "unified_diff": "@@ -1,26 +1,26 @@\n probe::signal.send
probe::signal.send
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send — \n Signal being sent to a process\n-

Synopsis

signal.send

Values

name

\n- The name of the function used to send out the signal\n-

sinfo

\n- The address of siginfo struct\n-

sig_pid

\n+

Synopsis

signal.send

Values

sig_pid

\n The PID of the process receiving the signal\n-

sig_name

\n- A string representation of the signal\n+

name

\n+ The name of the function used to send out the signal\n+

shared

\n+ Indicates whether the signal is shared by the thread group\n+

si_code

\n+ Indicates the signal type\n

send2queue

\n Indicates whether the signal is sent to an existing\n sigqueue (deprecated in SystemTap 2.1)\n-

si_code

\n- Indicates the signal type\n+

sig_name

\n+ A string representation of the signal\n+

sinfo

\n+ The address of siginfo struct\n

sig

\n The number of the signal\n

task

\n A task handle to the signal recipient\n

pid_name

\n The name of the signal recipient\n-

shared

\n- Indicates whether the signal is shared by the thread group\n

Context

\n The signal's sender.\n

Prev Up Next
probe::signal.procmask.return Home probe::signal.send.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tgkill-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tgkill-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.sys_tgkill.return
probe::signal.sys_tgkill.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.sys_tgkill.return — \n Sending kill signal to a thread group completed\n-

Synopsis

signal.sys_tgkill.return

Values

retstr

\n- The return value to either __group_send_sig_info,\n-

name

\n+

Synopsis

signal.sys_tgkill.return

Values

name

\n Name of the probe point\n+

retstr

\n+ The return value to either __group_send_sig_info,\n

Prev Up Next
probe::signal.sys_tgkill Home probe::signal.sys_tkill
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tgkill.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tgkill.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::signal.sys_tgkill
probe::signal.sys_tgkill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.sys_tgkill — \n Sending kill signal to a thread group\n-

Synopsis

signal.sys_tgkill

Values

sig

\n+

Synopsis

signal.sys_tgkill

Values

sig_pid

\n+ The PID of the thread receiving the kill signal\n+

name

\n+ Name of the probe point\n+

task

\n+ A task handle to the signal recipient\n+

sig

\n The specific kill signal sent to the process\n+

pid_name

\n+ The name of the signal recipient\n

sig_name

\n A string representation of the signal\n-

name

\n- Name of the probe point\n-

sig_pid

\n- The PID of the thread receiving the kill signal\n

tgid

\n The thread group ID of the thread receiving the kill signal\n-

pid_name

\n- The name of the signal recipient\n-

task

\n- A task handle to the signal recipient\n

Description

\n The tgkill call is similar to tkill,\n except that it also allows the caller to specify the thread group ID of\n the thread to be signalled. This protects against TID reuse.\n

Prev Up Next
probe::signal.send_sig_queue.return Home probe::signal.sys_tgkill.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tkill.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tkill.html", "unified_diff": "@@ -1,20 +1,20 @@\n probe::signal.sys_tkill
probe::signal.sys_tkill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.sys_tkill — \n Sending a kill signal to a thread\n-

Synopsis

signal.sys_tkill

Values

name

\n- Name of the probe point\n-

sig_pid

\n- The PID of the process receiving the kill signal\n-

sig_name

\n+

Synopsis

signal.sys_tkill

Values

sig_name

\n A string representation of the signal\n-

sig

\n- The specific signal sent to the process\n-

task

\n- A task handle to the signal recipient\n

pid_name

\n The name of the signal recipient\n+

task

\n+ A task handle to the signal recipient\n+

sig

\n+ The specific signal sent to the process\n+

name

\n+ Name of the probe point\n+

sig_pid

\n+ The PID of the process receiving the kill signal\n

Description

\n The tkill call is analogous to kill(2),\n except that it also allows a process within a specific thread group to\n be targeted. Such processes are targeted through their unique\n thread IDs (TID).\n

Prev Up Next
probe::signal.sys_tgkill.return Home probe::signal.syskill
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-syskill.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-syskill.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::signal.syskill
probe::signal.syskill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.syskill — \n Sending kill signal to a process\n-

Synopsis

signal.syskill

Values

task

\n- A task handle to the signal recipient\n+

Synopsis

signal.syskill

Values

sig_name

\n+ A string representation of the signal\n

pid_name

\n The name of the signal recipient\n-

name

\n- Name of the probe point\n-

sig_pid

\n- The PID of the process receiving the signal\n-

sig_name

\n- A string representation of the signal\n+

task

\n+ A task handle to the signal recipient\n

sig

\n The specific signal sent to the process\n+

sig_pid

\n+ The PID of the process receiving the signal\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.sys_tkill Home probe::signal.syskill.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-systkill-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-systkill-return.html", "unified_diff": "@@ -1,7 +1,7 @@\n probe::signal.systkill.return
probe::signal.systkill.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.systkill.return — \n Sending kill signal to a thread completed\n-

Synopsis

signal.systkill.return

Values

name

\n- Name of the probe point\n-

retstr

\n+

Synopsis

signal.systkill.return

Values

retstr

\n The return value to either __group_send_sig_info,\n+

name

\n+ Name of the probe point\n

Prev Up Next
probe::signal.syskill.return Home probe::signal.wakeup
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-signal-wakeup.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-signal-wakeup.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::signal.wakeup
probe::signal.wakeup
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.wakeup — \n Sleeping process being wakened for signal\n-

Synopsis

signal.wakeup

Values

state_mask

\n+

Synopsis

signal.wakeup

Values

sig_pid

\n+ The PID of the process to wake\n+

state_mask

\n A string representation indicating the mask\n of task states to wake. Possible values are\n TASK_INTERRUPTIBLE, TASK_STOPPED,\n TASK_TRACED, TASK_WAKEKILL, and TASK_INTERRUPTIBLE.\n-

sig_pid

\n- The PID of the process to wake\n+

pid_name

\n+ Name of the process to wake\n

resume

\n Indicates whether to wake up a task in a\n STOPPED or TRACED state\n-

pid_name

\n- Name of the process to wake\n

Prev Up Next
probe::signal.systkill.return Home Chapter 18. Errno Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.aio_read.return
probe::socket.aio_read.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_read.return — \n Conclusion of message received via sock_aio_read\n-

Synopsis

socket.aio_read.return

Values

size

\n+

Synopsis

socket.aio_read.return

Values

success

\n+ Was receive successful? (1 = yes, 0 = no)\n+

family

\n+ Protocol family value\n+

size

\n Size of message received (in bytes) or error code if success = 0\n

type

\n Socket type value\n-

state

\n- Socket state value\n

flags

\n Socket flags value\n

protocol

\n Protocol value\n+

state

\n+ Socket state value\n

name

\n Name of this probe\n-

success

\n- Was receive successful? (1 = yes, 0 = no)\n-

family

\n- Protocol family value\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of receiving a message on a socket\n via the sock_aio_read function\n

Prev Up Next
probe::socket.aio_read Home probe::socket.aio_write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.aio_read
probe::socket.aio_read
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_read — \n Receiving message via sock_aio_read\n

Synopsis

socket.aio_read

Values

type

\n Socket type value\n

size

\n Message size in bytes\n-

protocol

\n- Protocol value\n-

state

\n- Socket state value\n

flags

\n Socket flags value\n

family

\n Protocol family value\n

name

\n Name of this probe\n+

state

\n+ Socket state value\n+

protocol

\n+ Protocol value\n

Context

\n The message sender\n

Description

\n Fires at the beginning of receiving a message on a socket\n via the sock_aio_read function\n

Prev Up Next
function::sock_state_str2num Home probe::socket.aio_read.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write-return.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::socket.aio_write.return
probe::socket.aio_write.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_write.return — \n Conclusion of message send via sock_aio_write\n-

Synopsis

socket.aio_write.return

Values

size

\n- Size of message received (in bytes) or error code if success = 0\n+

Synopsis

socket.aio_write.return

Values

success

\n+ Was receive successful? (1 = yes, 0 = no)\n+

flags

\n+ Socket flags value\n

type

\n Socket type value\n-

name

\n- Name of this probe\n-

success

\n- Was receive successful? (1 = yes, 0 = no)\n+

size

\n+ Size of message received (in bytes) or error code if success = 0\n

family

\n Protocol family value\n-

flags

\n- Socket flags value\n+

name

\n+ Name of this probe\n

state

\n Socket state value\n

protocol

\n Protocol value\n

Context

\n The message receiver.\n

Description

\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.aio_write

probe::socket.aio_write
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_write — \n Message send via sock_aio_write\n-

Synopsis

socket.aio_write

Values

size

\n- Message size in bytes\n-

type

\n+

Synopsis

socket.aio_write

Values

type

\n Socket type value\n-

name

\n- Name of this probe\n-

family

\n- Protocol family value\n+

size

\n+ Message size in bytes\n

flags

\n Socket flags value\n-

state

\n- Socket state value\n+

family

\n+ Protocol family value\n+

name

\n+ Name of this probe\n

protocol

\n Protocol value\n+

state

\n+ Socket state value\n

Context

\n The message sender\n

Description

\n Fires at the beginning of sending a message on a socket\n via the sock_aio_write function\n

Prev Up Next
probe::socket.aio_read.return Home probe::socket.aio_write.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-close.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-close.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::socket.close
probe::socket.close
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.close — \n Close a socket\n-

Synopsis

socket.close

Values

type

\n- Socket type value\n-

family

\n- Protocol family value\n-

name

\n+

Synopsis

socket.close

Values

name

\n Name of this probe\n-

protocol

\n- Protocol value\n

state

\n Socket state value\n+

protocol

\n+ Protocol value\n

flags

\n Socket flags value\n+

type

\n+ Socket type value\n+

family

\n+ Protocol family value\n

Context

\n The requester (user process or kernel)\n

Description

\n Fires at the beginning of closing a socket.\n

Prev Up Next
probe::socket.aio_write.return Home probe::socket.close.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-create-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-create-return.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::socket.create.return
probe::socket.create.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.create.return — \n Return from Creation of a socket\n-

Synopsis

socket.create.return

Values

type

\n- Socket type value\n-

requester

\n- Requested by user process or the kernel (1 = kernel, 0 = user)\n-

protocol

\n- Protocol value\n+

Synopsis

socket.create.return

Values

success

\n+ Was socket creation successful? (1 = yes, 0 = no)\n

err

\n Error code if success == 0\n-

family

\n- Protocol family value\n-

success

\n- Was socket creation successful? (1 = yes, 0 = no)\n

name

\n Name of this probe\n+

protocol

\n+ Protocol value\n+

requester

\n+ Requested by user process or the kernel (1 = kernel, 0 = user)\n+

type

\n+ Socket type value\n+

family

\n+ Protocol family value\n

Context

\n The requester (user process or kernel)\n

Description

\n Fires at the conclusion of creating a socket.\n

Prev Up Next
probe::socket.create Home probe::socket.read_iter
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-create.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-create.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::socket.create
probe::socket.create
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.create — \n Creation of a socket\n-

Synopsis

socket.create

Values

type

\n+

Synopsis

socket.create

Values

name

\n+ Name of this probe\n+

protocol

\n+ Protocol value\n+

type

\n Socket type value\n

requester

\n Requested by user process or the kernel (1 = kernel, 0 = user)\n-

protocol

\n- Protocol value\n

family

\n Protocol family value\n-

name

\n- Name of this probe\n

Context

\n The requester (see requester variable)\n

Description

\n Fires at the beginning of creating a socket.\n

Prev Up Next
probe::socket.close.return Home probe::socket.create.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.read_iter.return
probe::socket.read_iter.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.read_iter.return — \n Conclusion of message received via sock_read_iter\n-

Synopsis

socket.read_iter.return

Values

size

\n- Size of message received (in bytes) or error code if success = 0\n-

type

\n- Socket type value\n-

success

\n+

Synopsis

socket.read_iter.return

Values

success

\n Was receive successful? (1 = yes, 0 = no)\n-

family

\n- Protocol family value\n

name

\n Name of this probe\n-

protocol

\n- Protocol value\n

state

\n Socket state value\n+

protocol

\n+ Protocol value\n+

size

\n+ Size of message received (in bytes) or error code if success = 0\n+

type

\n+ Socket type value\n

flags

\n Socket flags value\n+

family

\n+ Protocol family value\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of receiving a message on a socket\n via the sock_read_iter function\n

Prev Up Next
probe::socket.read_iter Home probe::socket.readv
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.read_iter
probe::socket.read_iter
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.read_iter — \n Receiving message via sock_read_iter\n

Synopsis

socket.read_iter

Values

state

\n Socket state value\n-

flags

\n- Socket flags value\n

protocol

\n Protocol value\n

name

\n Name of this probe\n

family

\n Protocol family value\n-

size

\n- Message size in bytes\n

type

\n Socket type value\n+

size

\n+ Message size in bytes\n+

flags

\n+ Socket flags value\n

Context

\n The message sender\n

Description

\n Fires at the beginning of receiving a message on a socket\n via the sock_read_iter function\n

Prev Up Next
probe::socket.create.return Home probe::socket.read_iter.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-readv-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-readv-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.readv.return
probe::socket.readv.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.readv.return — \n Conclusion of receiving a message via sock_readv\n-

Synopsis

socket.readv.return

Values

type

\n- Socket type value\n-

size

\n- Size of message received (in bytes) or error code if success = 0\n+

Synopsis

socket.readv.return

Values

name

\n+ Name of this probe\n

protocol

\n Protocol value\n-

flags

\n- Socket flags value\n

state

\n Socket state value\n+

flags

\n+ Socket flags value\n+

type

\n+ Socket type value\n+

size

\n+ Size of message received (in bytes) or error code if success = 0\n

family

\n Protocol family value\n

success

\n Was receive successful? (1 = yes, 0 = no)\n-

name

\n- Name of this probe\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of receiving a message on a socket\n via the sock_readv function\n

Prev Up Next
probe::socket.readv Home probe::socket.receive
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-readv.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-readv.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::socket.readv
probe::socket.readv
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.readv — \n Receiving a message via sock_readv\n-

Synopsis

socket.readv

Values

type

\n- Socket type value\n-

size

\n- Message size in bytes\n+

Synopsis

socket.readv

Values

name

\n+ Name of this probe\n

state

\n Socket state value\n-

flags

\n- Socket flags value\n

protocol

\n Protocol value\n-

name

\n- Name of this probe\n+

size

\n+ Message size in bytes\n+

type

\n+ Socket type value\n+

flags

\n+ Socket flags value\n

family

\n Protocol family value\n

Context

\n The message sender\n

Description

\n Fires at the beginning of receiving a message on a socket\n via the sock_readv function\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-receive.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-receive.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::socket.receive

probe::socket.receive
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.receive — \n Message received on a socket.\n-

Synopsis

socket.receive

Values

size

\n+

Synopsis

socket.receive

Values

family

\n+ Protocol family value\n+

size

\n Size of message received (in bytes) or error code if success = 0\n

type

\n Socket type value\n

flags

\n Socket flags value\n

state

\n Socket state value\n

protocol

\n Protocol value\n

name

\n Name of this probe\n

success

\n Was send successful? (1 = yes, 0 = no)\n-

family

\n- Protocol family value\n

Context

\n The message receiver\n

Prev Up Next
probe::socket.readv.return Home probe::socket.recvmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.recvmsg.return
probe::socket.recvmsg.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.recvmsg.return — \n Return from Message being received on socket\n-

Synopsis

socket.recvmsg.return

Values

size

\n- Size of message received (in bytes) or error code if success = 0\n-

type

\n- Socket type value\n-

protocol

\n- Protocol value\n+

Synopsis

socket.recvmsg.return

Values

success

\n+ Was receive successful? (1 = yes, 0 = no)\n

flags

\n Socket flags value\n-

state

\n- Socket state value\n+

type

\n+ Socket type value\n+

size

\n+ Size of message received (in bytes) or error code if success = 0\n

family

\n Protocol family value\n-

success

\n- Was receive successful? (1 = yes, 0 = no)\n

name

\n Name of this probe\n+

state

\n+ Socket state value\n+

protocol

\n+ Protocol value\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of receiving a message on a socket\n via the sock_recvmsg function.\n

Prev Up Next
probe::socket.recvmsg Home probe::socket.send
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.recvmsg
probe::socket.recvmsg
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.recvmsg — \n Message being received on socket\n-

Synopsis

socket.recvmsg

Values

type

\n- Socket type value\n-

size

\n- Message size in bytes\n-

name

\n+

Synopsis

socket.recvmsg

Values

name

\n Name of this probe\n-

family

\n- Protocol family value\n

state

\n Socket state value\n-

flags

\n- Socket flags value\n

protocol

\n Protocol value\n+

flags

\n+ Socket flags value\n+

size

\n+ Message size in bytes\n+

type

\n+ Socket type value\n+

family

\n+ Protocol family value\n

Context

\n The message receiver.\n

Description

\n Fires at the beginning of receiving a message on a socket\n via the sock_recvmsg function\n

Prev Up Next
probe::socket.receive Home probe::socket.recvmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-send.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-send.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,21 +1,21 @@\n probe::socket.send
probe::socket.send
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.send — \n Message sent on a socket.\n

Synopsis

socket.send

Values

size

\n Size of message sent (in bytes) or error code if success = 0\n

type

\n Socket type value\n-

state

\n- Socket state value\n

flags

\n Socket flags value\n-

protocol

\n- Protocol value\n-

name

\n- Name of this probe\n

family

\n Protocol family value\n+

name

\n+ Name of this probe\n+

state

\n+ Socket state value\n+

protocol

\n+ Protocol value\n

success

\n Was send successful? (1 = yes, 0 = no)\n

Context

\n The message sender\n

Prev Up Next
probe::socket.recvmsg.return Home probe::socket.sendmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.sendmsg.return
probe::socket.sendmsg.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.sendmsg.return — \n Return from socket.sendmsg.\n-

Synopsis

socket.sendmsg.return

Values

type

\n- Socket type value\n-

size

\n- Size of message sent (in bytes) or error code if success = 0\n-

success

\n+

Synopsis

socket.sendmsg.return

Values

success

\n Was send successful? (1 = yes, 0 = no)\n-

family

\n- Protocol family value\n-

name

\n- Name of this probe\n+

state

\n+ Socket state value\n

protocol

\n Protocol value\n+

name

\n+ Name of this probe\n+

family

\n+ Protocol family value\n+

size

\n+ Size of message sent (in bytes) or error code if success = 0\n+

type

\n+ Socket type value\n

flags

\n Socket flags value\n-

state

\n- Socket state value\n

Context

\n The message sender.\n

Description

\n Fires at the conclusion of sending a message on a socket\n via the sock_sendmsg function\n

Prev Up Next
probe::socket.sendmsg Home probe::socket.write_iter
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.sendmsg
probe::socket.sendmsg
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.sendmsg — \n Message is currently being sent on a socket.\n-

Synopsis

socket.sendmsg

Values

type

\n- Socket type value\n-

size

\n- Message size in bytes\n-

name

\n- Name of this probe\n-

family

\n+

Synopsis

socket.sendmsg

Values

family

\n Protocol family value\n

flags

\n Socket flags value\n-

state

\n- Socket state value\n+

type

\n+ Socket type value\n+

size

\n+ Message size in bytes\n

protocol

\n Protocol value\n+

state

\n+ Socket state value\n+

name

\n+ Name of this probe\n

Context

\n The message sender\n

Description

\n Fires at the beginning of sending a message on a socket\n via the sock_sendmsg function\n

Prev Up Next
probe::socket.send Home probe::socket.sendmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.write_iter.return
probe::socket.write_iter.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.write_iter.return — \n Conclusion of message send via sock_write_iter\n-

Synopsis

socket.write_iter.return

Values

size

\n- Size of message received (in bytes) or error code if success = 0\n-

type

\n- Socket type value\n+

Synopsis

socket.write_iter.return

Values

name

\n+ Name of this probe\n

protocol

\n Protocol value\n

state

\n Socket state value\n+

size

\n+ Size of message received (in bytes) or error code if success = 0\n+

type

\n+ Socket type value\n

flags

\n Socket flags value\n-

success

\n- Was receive successful? (1 = yes, 0 = no)\n

family

\n Protocol family value\n-

name

\n- Name of this probe\n+

success

\n+ Was receive successful? (1 = yes, 0 = no)\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of sending a message on a socket\n via the sock_write_iter function\n

Prev Up Next
probe::socket.write_iter Home probe::socket.writev
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.write_iter
probe::socket.write_iter
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.write_iter — \n Message send via sock_write_iter\n-

Synopsis

socket.write_iter

Values

size

\n- Message size in bytes\n-

type

\n- Socket type value\n-

family

\n- Protocol family value\n-

name

\n- Name of this probe\n+

Synopsis

socket.write_iter

Values

state

\n+ Socket state value\n

protocol

\n Protocol value\n-

state

\n- Socket state value\n+

name

\n+ Name of this probe\n+

family

\n+ Protocol family value\n

flags

\n Socket flags value\n+

size

\n+ Message size in bytes\n+

type

\n+ Socket type value\n

Context

\n The message sender\n

Description

\n Fires at the beginning of sending a message on a socket\n via the sock_write_iter function\n

Prev Up Next
probe::socket.sendmsg.return Home probe::socket.write_iter.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-writev-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-writev-return.html", "unified_diff": "@@ -1,24 +1,24 @@\n probe::socket.writev.return
probe::socket.writev.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.writev.return — \n Conclusion of message sent via socket_writev\n-

Synopsis

socket.writev.return

Values

size

\n- Size of message sent (in bytes) or error code if success = 0\n+

Synopsis

socket.writev.return

Values

family

\n+ Protocol family value\n+

flags

\n+ Socket flags value\n

type

\n Socket type value\n+

size

\n+ Size of message sent (in bytes) or error code if success = 0\n

protocol

\n Protocol value\n

state

\n Socket state value\n-

flags

\n- Socket flags value\n-

family

\n- Protocol family value\n-

success

\n- Was send successful? (1 = yes, 0 = no)\n

name

\n Name of this probe\n+

success

\n+ Was send successful? (1 = yes, 0 = no)\n

Context

\n The message receiver.\n

Description

\n Fires at the conclusion of sending a message on a socket\n via the sock_writev function\n

Prev Up Next
probe::socket.writev Home Chapter 15. SNMP Information Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-socket-writev.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-socket-writev.html", "unified_diff": "@@ -1,22 +1,22 @@\n probe::socket.writev
probe::socket.writev
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.writev — \n Message sent via socket_writev\n-

Synopsis

socket.writev

Values

type

\n- Socket type value\n-

size

\n- Message size in bytes\n-

name

\n- Name of this probe\n-

family

\n+

Synopsis

socket.writev

Values

family

\n Protocol family value\n

flags

\n Socket flags value\n+

size

\n+ Message size in bytes\n+

type

\n+ Socket type value\n

state

\n Socket state value\n

protocol

\n Protocol value\n+

name

\n+ Name of this probe\n

Context

\n The message sender\n

Description

\n Fires at the beginning of sending a message on a socket\n via the sock_writev function\n

Prev Up Next
probe::socket.write_iter.return Home probe::socket.writev.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-softirq-entry.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-softirq-entry.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::softirq.entry
probe::softirq.entry
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::softirq.entry — \n Execution of handler for a pending softirq starting\n-

Synopsis

softirq.entry

Values

vec_nr

\n+

Synopsis

softirq.entry

Values

h

\n+ struct softirq_action* for current pending softirq\n+

vec_nr

\n softirq vector number\n

vec

\n softirq_action vector\n

action

\n pointer to softirq handler just about to execute\n-

h

\n- struct softirq_action* for current pending softirq\n

Prev Up Next
probe::irq_handler.exit Home probe::softirq.exit
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-softirq-exit.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-softirq-exit.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::softirq.exit
probe::softirq.exit
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::softirq.exit — \n Execution of handler for a pending softirq completed\n-

Synopsis

softirq.exit

Values

vec

\n+

Synopsis

softirq.exit

Values

h

\n+ struct softirq_action* for just executed softirq\n+

vec

\n softirq_action vector\n

action

\n pointer to softirq handler that just finished execution\n-

h

\n- struct softirq_action* for just executed softirq\n

vec_nr

\n softirq vector number\n

Prev Up Next
probe::softirq.entry Home probe::workqueue.create
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-mod.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-mod.html", "unified_diff": "@@ -1,10 +1,10 @@\n probe::stap.cache_add_mod
probe::stap.cache_add_mod
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_add_mod — \n Adding kernel instrumentation module to cache\n-

Synopsis

stap.cache_add_mod

Values

source_path

\n- the path the .ko file is coming from (incl filename)\n-

dest_path

\n+

Synopsis

stap.cache_add_mod

Values

dest_path

\n the path the .ko file is going to (incl filename)\n+

source_path

\n+ the path the .ko file is coming from (incl filename)\n

Description

\n Fires just before the file is actually moved. Note: if moving fails,\n cache_add_src and cache_add_nss will not fire.\n

Prev Up Next
Chapter 30. SystemTap Translator Tapset Home probe::stap.cache_add_nss
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-nss.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-nss.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::stap.cache_add_nss
probe::stap.cache_add_nss
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_add_nss — \n Add NSS (Network Security Services) information to cache\n-

Synopsis

stap.cache_add_nss

Values

source_path

\n+

Synopsis

stap.cache_add_nss

Values

dest_path

\n the path the .sgn file is coming from (incl filename)\n-

dest_path

\n+

source_path

\n the path the .sgn file is coming from (incl filename)\n

Description

\n Fires just before the file is actually moved. Note: stap must compiled\n with NSS support; if moving the kernel module fails, this probe will\n not fire.\n

Prev Up Next
probe::stap.cache_add_mod Home probe::stap.cache_add_src
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-src.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-src.html", "unified_diff": "@@ -1,10 +1,10 @@\n probe::stap.cache_add_src
probe::stap.cache_add_src
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_add_src — \n Adding C code translation to cache\n-

Synopsis

stap.cache_add_src

Values

dest_path

\n- the path the .c file is going to (incl filename)\n-

source_path

\n+

Synopsis

stap.cache_add_src

Values

source_path

\n the path the .c file is coming from (incl filename)\n+

dest_path

\n+ the path the .c file is going to (incl filename)\n

Description

\n Fires just before the file is actually moved. Note: if moving the\n kernel module fails, this probe will not fire.\n

Prev Up Next
probe::stap.cache_add_nss Home probe::stap.cache_clean
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-get.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-get.html", "unified_diff": "@@ -1,10 +1,10 @@\n probe::stap.cache_get
probe::stap.cache_get
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_get — \n Found item in stap cache\n-

Synopsis

stap.cache_get

Values

module_path

\n- the path of the .ko kernel module file\n-

source_path

\n+

Synopsis

stap.cache_get

Values

source_path

\n the path of the .c source file\n+

module_path

\n+ the path of the .ko kernel module file\n

Description

\n Fires just before the return of get_from_cache, when the cache grab\n is successful.\n

Prev Up Next
probe::stap.cache_clean Home probe::stap.pass0
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stap-system-spawn.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stap-system-spawn.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::stap.system.spawn
probe::stap.system.spawn
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.system.spawn — \n stap spawned new process\n-

Synopsis

stap.system.spawn

Values

pid

\n- the pid of the spawned process\n-

ret

\n+

Synopsis

stap.system.spawn

Values

ret

\n the return value from posix_spawn\n+

pid

\n+ the pid of the spawned process\n

Description

\n Fires just after the call to posix_spawn.\n

Prev Up Next
probe::stap.system.return Home probe::stapio.receive_control_message
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-stapio-receive-control-message.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-stapio-receive-control-message.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::stapio.receive_control_message
probe::stapio.receive_control_message
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stapio.receive_control_message — \n Received a control message\n-

Synopsis

stapio.receive_control_message

Values

type

\n- type of message being send; defined in runtime/transport/transport_msgs.h\n-

data

\n+

Synopsis

stapio.receive_control_message

Values

data

\n a ptr to a binary blob of data sent as the control message\n

len

\n the length (in bytes) of the data blob\n+

type

\n+ type of message being send; defined in runtime/transport/transport_msgs.h\n

Description

\n Fires just after a message was receieved and before it's processed.\n

Prev Up Next
probe::stap.system.spawn Home probe::staprun.insert_module
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-staprun-send-control-message.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-staprun-send-control-message.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::staprun.send_control_message
probe::staprun.send_control_message
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::staprun.send_control_message — \n Sending a control message\n-

Synopsis

staprun.send_control_message

Values

data

\n+

Synopsis

staprun.send_control_message

Values

type

\n+ type of message being send; defined in runtime/transport/transport_msgs.h\n+

data

\n a ptr to a binary blob of data sent as the control message\n

len

\n the length (in bytes) of the data blob\n-

type

\n- type of message being send; defined in runtime/transport/transport_msgs.h\n

Description

\n Fires at the beginning of the send_request function.\n

Prev Up Next
probe::staprun.remove_module Home Chapter 31. Network File Storage Tapsets
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-bind-new-program.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-bind-new-program.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.clnt.bind_new_program
probe::sunrpc.clnt.bind_new_program
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.bind_new_program — \n Bind a new RPC program to an existing client\n-

Synopsis

sunrpc.clnt.bind_new_program

Values

old_vers

\n- the version of old RPC program\n-

vers

\n- the version of new RPC program\n-

prog

\n+

Synopsis

sunrpc.clnt.bind_new_program

Values

prog

\n the number of new RPC program\n-

old_progname

\n- the name of old RPC program\n-

old_prog

\n- the number of old RPC program\n

servername

\n the server machine name\n+

old_prog

\n+ the number of old RPC program\n+

old_progname

\n+ the name of old RPC program\n+

old_vers

\n+ the version of old RPC program\n

progname

\n the name of new RPC program\n+

vers

\n+ the version of new RPC program\n

Prev Up Next
probe::netfilter.ip.pre_routing Home probe::sunrpc.clnt.call_async
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-async.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-async.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::sunrpc.clnt.call_async
probe::sunrpc.clnt.call_async
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.call_async — \n Make an asynchronous RPC call\n-

Synopsis

sunrpc.clnt.call_async

Values

progname

\n- the RPC program name\n+

Synopsis

sunrpc.clnt.call_async

Values

proc

\n+ the procedure number in this RPC call\n+

flags

\n+ flags\n+

dead

\n+ whether this client is abandoned\n

prot

\n the IP protocol number\n+

prog

\n+ the RPC program number\n+

xid

\n+ current transmission id\n

servername

\n the server machine name\n

port

\n the port number\n-

procname

\n- the procedure name in this RPC call\n-

prog

\n- the RPC program number\n

vers

\n the RPC program version number\n-

flags

\n- flags\n-

proc

\n- the procedure number in this RPC call\n-

xid

\n- current transmission id\n-

dead

\n- whether this client is abandoned\n+

procname

\n+ the procedure name in this RPC call\n+

progname

\n+ the RPC program name\n

Prev Up Next
probe::sunrpc.clnt.bind_new_program Home probe::sunrpc.clnt.call_sync
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-sync.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-sync.html", "unified_diff": "@@ -1,25 +1,25 @@\n probe::sunrpc.clnt.call_sync
probe::sunrpc.clnt.call_sync
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.call_sync — \n Make a synchronous RPC call\n-

Synopsis

sunrpc.clnt.call_sync

Values

xid

\n- current transmission id\n-

dead

\n- whether this client is abandoned\n-

proc

\n+

Synopsis

sunrpc.clnt.call_sync

Values

proc

\n the procedure number in this RPC call\n

flags

\n flags\n-

vers

\n- the RPC program version number\n+

dead

\n+ whether this client is abandoned\n+

prot

\n+ the IP protocol number\n

prog

\n the RPC program number\n-

procname

\n- the procedure name in this RPC call\n-

port

\n- the port number\n+

xid

\n+ current transmission id\n

servername

\n the server machine name\n-

prot

\n- the IP protocol number\n+

port

\n+ the port number\n+

procname

\n+ the procedure name in this RPC call\n+

vers

\n+ the RPC program version number\n

progname

\n the RPC program name\n

Prev Up Next
probe::sunrpc.clnt.call_async Home probe::sunrpc.clnt.clone_client
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-clone-client.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-clone-client.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.clnt.clone_client
probe::sunrpc.clnt.clone_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.clone_client — \n Clone an RPC client structure\n-

Synopsis

sunrpc.clnt.clone_client

Values

servername

\n- the server machine name\n-

progname

\n+

Synopsis

sunrpc.clnt.clone_client

Values

progname

\n the RPC program name\n-

prot

\n- the IP protocol number\n-

port

\n- the port number\n-

prog

\n- the RPC program number\n

vers

\n the RPC program version number\n

authflavor

\n the authentication flavor\n+

servername

\n+ the server machine name\n+

port

\n+ the port number\n+

prog

\n+ the RPC program number\n+

prot

\n+ the IP protocol number\n

Prev Up Next
probe::sunrpc.clnt.call_sync Home probe::sunrpc.clnt.create_client
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-create-client.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-create-client.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.clnt.create_client
probe::sunrpc.clnt.create_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.create_client — \n Create an RPC client\n-

Synopsis

sunrpc.clnt.create_client

Values

progname

\n- the RPC program name\n+

Synopsis

sunrpc.clnt.create_client

Values

port

\n+ the port number\n

prot

\n the IP protocol number\n-

servername

\n- the server machine name\n-

port

\n- the port number\n

prog

\n the RPC program number\n+

progname

\n+ the RPC program name\n

vers

\n the RPC program version number\n

authflavor

\n the authentication flavor\n+

servername

\n+ the server machine name\n

Prev Up Next
probe::sunrpc.clnt.clone_client Home probe::sunrpc.clnt.restart_call
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-restart-call.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-restart-call.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.clnt.restart_call
probe::sunrpc.clnt.restart_call
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.restart_call — \n Restart an asynchronous RPC call\n-

Synopsis

sunrpc.clnt.restart_call

Values

prog

\n- the RPC program number\n-

tk_pid

\n- the debugging aid of task\n-

xid

\n- the transmission id\n-

servername

\n+

Synopsis

sunrpc.clnt.restart_call

Values

servername

\n the server machine name\n

tk_flags

\n the task flags\n-

tk_priority

\n- the task priority\n+

xid

\n+ the transmission id\n

tk_runstate

\n the task run status\n+

prog

\n+ the RPC program number\n+

tk_priority

\n+ the task priority\n+

tk_pid

\n+ the debugging aid of task\n

Prev Up Next
probe::sunrpc.clnt.create_client Home probe::sunrpc.clnt.shutdown_client
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-shutdown-client.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-shutdown-client.html", "unified_diff": "@@ -1,39 +1,39 @@\n probe::sunrpc.clnt.shutdown_client
probe::sunrpc.clnt.shutdown_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.shutdown_client — \n Shutdown an RPC client\n-

Synopsis

sunrpc.clnt.shutdown_client

Values

prog

\n- the RPC program number\n-

om_ops

\n- the count of operations\n-

om_ntrans

\n- the count of RPC transmissions\n-

om_bytes_sent

\n- the count of bytes out\n-

netreconn

\n- the count of reconnections\n-

clones

\n- the number of clones\n-

vers

\n- the RPC program version number\n-

om_rtt

\n- the RPC RTT jiffies\n+

Synopsis

sunrpc.clnt.shutdown_client

Values

port

\n+ the port number\n

om_bytes_recv

\n the count of bytes in\n-

port

\n- the port number\n+

vers

\n+ the RPC program version number\n

om_execute

\n the RPC execution jiffies\n-

prot

\n- the IP protocol number\n-

rpccnt

\n- the count of RPC calls\n+

tasks

\n+ the number of references\n

progname

\n the RPC program name\n+

rpccnt

\n+ the count of RPC calls\n

om_queue

\n the jiffies queued for xmit\n-

servername

\n- the server machine name\n-

tasks

\n- the number of references\n+

om_ntrans

\n+ the count of RPC transmissions\n+

om_bytes_sent

\n+ the count of bytes out\n

authflavor

\n the authentication flavor\n+

om_ops

\n+ the count of operations\n+

prot

\n+ the IP protocol number\n+

prog

\n+ the RPC program number\n+

netreconn

\n+ the count of reconnections\n+

clones

\n+ the number of clones\n+

servername

\n+ the server machine name\n+

om_rtt

\n+ the RPC RTT jiffies\n

Prev Up Next
probe::sunrpc.clnt.restart_call Home probe::sunrpc.sched.delay
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-delay.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-delay.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.sched.delay
probe::sunrpc.sched.delay
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.delay — \n Delay an RPC task\n-

Synopsis

sunrpc.sched.delay

Values

tk_flags

\n- the flags of the task\n-

prot

\n- the IP protocol in the RPC call\n+

Synopsis

sunrpc.sched.delay

Values

vers

\n+ the program version in the RPC call\n

tk_pid

\n the debugging id of the task\n+

delay

\n+ the time delayed\n

xid

\n the transmission id in the RPC call\n-

vers

\n- the program version in the RPC call\n+

prot

\n+ the IP protocol in the RPC call\n

prog

\n the program number in the RPC call\n-

delay

\n- the time delayed\n+

tk_flags

\n+ the flags of the task\n

Prev Up Next
probe::sunrpc.clnt.shutdown_client Home probe::sunrpc.sched.execute
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-execute.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-execute.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::sunrpc.sched.execute
probe::sunrpc.sched.execute
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.execute — \n Execute the RPC `scheduler'\n-

Synopsis

sunrpc.sched.execute

Values

prog

\n- the program number in the RPC call\n-

vers

\n+

Synopsis

sunrpc.sched.execute

Values

vers

\n the program version in the RPC call\n-

xid

\n- the transmission id in the RPC call\n

tk_pid

\n the debugging id of the task\n-

prot

\n- the IP protocol in the RPC call\n

tk_flags

\n the flags of the task\n+

xid

\n+ the transmission id in the RPC call\n+

prog

\n+ the program number in the RPC call\n+

prot

\n+ the IP protocol in the RPC call\n

Prev Up Next
probe::sunrpc.sched.delay Home probe::sunrpc.sched.new_task
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-new-task.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-new-task.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,13 +1,13 @@\n probe::sunrpc.sched.new_task
probe::sunrpc.sched.new_task
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.new_task — \n Create new task for the specified client\n

Synopsis

sunrpc.sched.new_task

Values

prog

\n the program number in the RPC call\n-

vers

\n- the program version in the RPC call\n-

xid

\n- the transmission id in the RPC call\n

prot

\n the IP protocol in the RPC call\n+

xid

\n+ the transmission id in the RPC call\n

tk_flags

\n the flags of the task\n+

vers

\n+ the program version in the RPC call\n

Prev Up Next
probe::sunrpc.sched.execute Home probe::sunrpc.sched.release_task
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-release-task.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-release-task.html", "unified_diff": "@@ -1,16 +1,16 @@\n probe::sunrpc.sched.release_task
probe::sunrpc.sched.release_task
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.release_task — \n Release all resources associated with a task\n-

Synopsis

sunrpc.sched.release_task

Values

prot

\n- the IP protocol in the RPC call\n-

tk_flags

\n+

Synopsis

sunrpc.sched.release_task

Values

tk_flags

\n the flags of the task\n+

xid

\n+ the transmission id in the RPC call\n

prog

\n the program number in the RPC call\n+

prot

\n+ the IP protocol in the RPC call\n

vers

\n the program version in the RPC call\n-

xid

\n- the transmission id in the RPC call\n

Description

\n rpc_release_task function might not be found for a particular kernel.\n So, if we can't find it, just return '-1' for everything.\n

Prev Up Next
probe::sunrpc.sched.new_task Home probe::sunrpc.svc.create
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-create.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-create.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::sunrpc.svc.create
probe::sunrpc.svc.create
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.create — \n Create an RPC service\n-

Synopsis

sunrpc.svc.create

Values

pg_nvers

\n+

Synopsis

sunrpc.svc.create

Values

bufsize

\n+ the buffer size\n+

prog

\n+ the number of the program\n+

pg_nvers

\n the number of supported versions\n

progname

\n the name of the program\n-

prog

\n- the number of the program\n-

bufsize

\n- the buffer size\n

Prev Up Next
probe::sunrpc.sched.release_task Home probe::sunrpc.svc.destroy
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-destroy.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-destroy.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::sunrpc.svc.destroy
probe::sunrpc.svc.destroy
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.destroy — \n Destroy an RPC service\n-

Synopsis

sunrpc.svc.destroy

Values

sv_prog

\n- the number of the program\n+

Synopsis

sunrpc.svc.destroy

Values

rpccnt

\n+ the count of valid RPC requests\n

nettcpconn

\n the count of accepted TCP connections\n

rpcbadfmt

\n the count of requests dropped for bad formats\n-

netcnt

\n- the count of received RPC requests\n-

rpcbadauth

\n- the count of requests drooped for authentication failure\n-

sv_nrthreads

\n- the number of concurrent threads\n

sv_name

\n the service name\n+

rpcbadauth

\n+ the count of requests drooped for authentication failure\n+

sv_prog

\n+ the number of the program\n

sv_progname

\n the name of the program\n-

rpccnt

\n- the count of valid RPC requests\n+

sv_nrthreads

\n+ the number of concurrent threads\n+

netcnt

\n+ the count of received RPC requests\n

Prev Up Next
probe::sunrpc.svc.create Home probe::sunrpc.svc.drop
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-drop.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-drop.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.svc.drop
probe::sunrpc.svc.drop
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.drop — \n Drop RPC request\n-

Synopsis

sunrpc.svc.drop

Values

rq_prog

\n- the program number in the request\n-

peer_ip

\n+

Synopsis

sunrpc.svc.drop

Values

peer_ip

\n the peer address where the request is from\n-

rq_proc

\n- the procedure number in the request\n-

rq_prot

\n- the IP protocol of the reqeust\n-

rq_xid

\n- the transmission id in the request\n

sv_name

\n the service name\n

rq_vers

\n the program version in the request\n+

rq_prot

\n+ the IP protocol of the reqeust\n+

rq_xid

\n+ the transmission id in the request\n+

rq_proc

\n+ the procedure number in the request\n+

rq_prog

\n+ the program number in the request\n

Prev Up Next
probe::sunrpc.svc.destroy Home probe::sunrpc.svc.process
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-process.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-process.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::sunrpc.svc.process
probe::sunrpc.svc.process
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.process — \n Process an RPC request\n-

Synopsis

sunrpc.svc.process

Values

rq_prog

\n- the program number in the request\n-

sv_prog

\n- the number of the program\n+

Synopsis

sunrpc.svc.process

Values

sv_name

\n+ the service name\n

peer_ip

\n the peer address where the request is from\n-

rq_proc

\n- the procedure number in the request\n-

rq_xid

\n- the transmission id in the request\n+

sv_nrthreads

\n+ the number of concurrent threads\n+

rq_prog

\n+ the program number in the request\n

rq_prot

\n the IP protocol of the reqeust\n-

sv_name

\n- the service name\n+

rq_xid

\n+ the transmission id in the request\n+

rq_proc

\n+ the procedure number in the request\n+

sv_prog

\n+ the number of the program\n

rq_vers

\n the program version in the request\n-

sv_nrthreads

\n- the number of concurrent threads\n

Prev Up Next
probe::sunrpc.svc.drop Home probe::sunrpc.svc.recv
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-recv.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-recv.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::sunrpc.svc.recv
probe::sunrpc.svc.recv
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.recv — \n Listen for the next RPC request on any socket\n-

Synopsis

sunrpc.svc.recv

Values

timeout

\n+

Synopsis

sunrpc.svc.recv

Values

sv_name

\n+ the service name\n+

timeout

\n the timeout of waiting for data\n-

sv_prog

\n- the number of the program\n

sv_nrthreads

\n the number of concurrent threads\n-

sv_name

\n- the service name\n+

sv_prog

\n+ the number of the program\n

Prev Up Next
probe::sunrpc.svc.process Home probe::sunrpc.svc.register
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-register.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-register.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::sunrpc.svc.register
probe::sunrpc.svc.register
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.register — \n Register an RPC service with the local portmapper\n-

Synopsis

sunrpc.svc.register

Values

prot

\n- the IP protocol number\n+

Synopsis

sunrpc.svc.register

Values

port

\n+ the port number\n

progname

\n the name of the program\n-

port

\n- the port number\n

sv_name

\n the service name\n

prog

\n the number of the program\n+

prot

\n+ the IP protocol number\n

Description

\n If proto and port are both 0, then unregister a service.\n

Prev Up Next
probe::sunrpc.svc.recv Home probe::sunrpc.svc.send
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-send.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-send.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::sunrpc.svc.send
probe::sunrpc.svc.send
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.send — \n Return reply to RPC client\n-

Synopsis

sunrpc.svc.send

Values

rq_vers

\n- the program version in the request\n-

sv_name

\n- the service name\n+

Synopsis

sunrpc.svc.send

Values

rq_prog

\n+ the program number in the request\n+

rq_proc

\n+ the procedure number in the request\n

rq_xid

\n the transmission id in the request\n

rq_prot

\n the IP protocol of the reqeust\n-

rq_proc

\n- the procedure number in the request\n+

rq_vers

\n+ the program version in the request\n+

sv_name

\n+ the service name\n

peer_ip

\n the peer address where the request is from\n-

rq_prog

\n- the program number in the request\n

Prev Up Next
probe::sunrpc.svc.register Home probe::tcp.disconnect
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-syscall-any-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-syscall-any-return.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::syscall_any.return
probe::syscall_any.return
Prev Chapter 36. Syscall Any Tapset Next

Name

probe::syscall_any.return — \n Record exit from a syscall\n-

Synopsis

syscall_any.return

Values

retval

\n- return value of the syscall\n+

Synopsis

syscall_any.return

Values

syscall_nr

\n+ number of the syscall\n

name

\n name of the syscall\n-

syscall_nr

\n- number of the syscall\n+

retval

\n+ return value of the syscall\n

Context

\n The process performing the syscall\n

Description

\n The syscall_any.return probe point is designed to be a low overhead\n that monitors all the syscalls returns via a kernel tracepoint.\n Because of the breadth of syscalls it monitors it provides\n no information about the syscall arguments, argstr string\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-syscall-any.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-syscall-any.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::syscall_any

probe::syscall_any
Prev Chapter 36. Syscall Any Tapset Next

Name

probe::syscall_any — \n Record entry into a syscall\n-

Synopsis

syscall_any

Values

syscall_nr

\n- number of the syscall\n-

name

\n+

Synopsis

syscall_any

Values

name

\n name of the syscall\n+

syscall_nr

\n+ number of the syscall\n

Context

\n The process performing the syscall\n

Description

\n The syscall_any probe point is designed to be a low overhead\n that monitors all the syscalls entered via a kernel tracepoint.\n Because of the breadth of syscalls it monitors it provides\n no information about the syscall arguments or argstr string\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-disconnect.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-disconnect.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::tcp.disconnect

probe::tcp.disconnect
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.disconnect — \n TCP socket disconnection\n-

Synopsis

tcp.disconnect

Values

daddr

\n- A string representing the destination IP address\n-

flags

\n- TCP flags (e.g. FIN, etc) \n+

Synopsis

tcp.disconnect

Values

sport

\n+ TCP source port \n+

name

\n+ Name of this probe\n

dport

\n TCP destination port\n+

daddr

\n+ A string representing the destination IP address\n

saddr

\n A string representing the source IP address\n-

sock

\n- Network socket \n-

sport

\n- TCP source port \n

family

\n IP address family\n-

name

\n- Name of this probe\n+

sock

\n+ Network socket \n+

flags

\n+ TCP flags (e.g. FIN, etc) \n

Context

\n The process which disconnects tcp \n

Prev Up Next
probe::sunrpc.svc.send Home probe::tcp.disconnect.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-receive.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-receive.html", "unified_diff": "@@ -1,31 +1,31 @@\n probe::tcp.receive
probe::tcp.receive
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.receive — \n Called when a TCP packet is received\n-

Synopsis

tcp.receive

Values

rst

\n- TCP RST flag\n-

family

\n- IP address family\n-

fin

\n+

Synopsis

tcp.receive

Values

fin

\n TCP FIN flag\n-

sport

\n- TCP source port\n

protocol

\n Packet protocol from driver\n-

saddr

\n- A string representing the source IP address\n+

daddr

\n+ A string representing the destination IP address\n+

family

\n+ IP address family\n

ack

\n TCP ACK flag\n-

psh

\n- TCP PSH flag\n-

name

\n- Name of the probe point\n+

sport

\n+ TCP source port\n+

rst

\n+ TCP RST flag\n

urg

\n TCP URG flag\n+

psh

\n+ TCP PSH flag\n+

saddr

\n+ A string representing the source IP address\n+

iphdr

\n+ IP header address\n

syn

\n TCP SYN flag\n+

name

\n+ Name of the probe point\n

dport

\n TCP destination port\n-

iphdr

\n- IP header address\n-

daddr

\n- A string representing the destination IP address\n

Prev Up Next
probe::tcp.disconnect.return Home probe::tcp.recvmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg-return.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::tcp.recvmsg.return
probe::tcp.recvmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.recvmsg.return — \n Receiving TCP message complete\n-

Synopsis

tcp.recvmsg.return

Values

name

\n- Name of this probe\n-

family

\n- IP address family\n-

sport

\n- TCP source port \n+

Synopsis

tcp.recvmsg.return

Values

size

\n+ Number of bytes received or error code if an error occurred.\n

saddr

\n A string representing the source IP address\n-

size

\n- Number of bytes received or error code if an error occurred.\n+

family

\n+ IP address family\n

dport

\n TCP destination port\n

daddr

\n A string representing the destination IP address\n+

name

\n+ Name of this probe\n+

sport

\n+ TCP source port \n

Context

\n The process which receives a tcp message\n

Prev Up Next
probe::tcp.recvmsg Home probe::tcp.sendmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::tcp.recvmsg
probe::tcp.recvmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.recvmsg — \n Receiving TCP message\n-

Synopsis

tcp.recvmsg

Values

daddr

\n- A string representing the destination IP address\n-

dport

\n+

Synopsis

tcp.recvmsg

Values

dport

\n TCP destination port\n

sock

\n Network socket\n-

saddr

\n- A string representing the source IP address\n

size

\n Number of bytes to be received \n-

name

\n- Name of this probe\n

family

\n IP address family\n+

saddr

\n+ A string representing the source IP address\n+

name

\n+ Name of this probe\n

sport

\n TCP source port \n+

daddr

\n+ A string representing the destination IP address\n

Context

\n The process which receives a tcp message\n

Prev Up Next
probe::tcp.receive Home probe::tcp.recvmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-sendmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-sendmsg.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::tcp.sendmsg
probe::tcp.sendmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.sendmsg — \n Sending a tcp message\n-

Synopsis

tcp.sendmsg

Values

size

\n+

Synopsis

tcp.sendmsg

Values

name

\n+ Name of this probe\n+

family

\n+ IP address family\n+

size

\n Number of bytes to send \n

sock

\n Network socket \n-

family

\n- IP address family\n-

name

\n- Name of this probe\n

Context

\n The process which sends a tcp message \n

Prev Up Next
probe::tcp.recvmsg.return Home probe::tcp.sendmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-setsockopt.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcp-setsockopt.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::tcp.setsockopt
probe::tcp.setsockopt
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.setsockopt — \n Call to setsockopt\n-

Synopsis

tcp.setsockopt

Values

family

\n+

Synopsis

tcp.setsockopt

Values

optstr

\n+ Resolves optname to a human-readable format\n+

family

\n IP address family\n-

name

\n- Name of this probe\n-

level

\n- The level at which the socket options will be manipulated\n

sock

\n Network socket\n-

optlen

\n- Used to access values for setsockopt\n+

level

\n+ The level at which the socket options will be manipulated\n

optname

\n TCP socket options (e.g. TCP_NODELAY, TCP_MAXSEG, etc)\n-

optstr

\n- Resolves optname to a human-readable format\n+

optlen

\n+ Used to access values for setsockopt\n+

name

\n+ Name of this probe\n

Context

\n The process which calls setsockopt\n

Prev Up Next
probe::tcp.sendmsg.return Home probe::tcp.setsockopt.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-ActiveOpens.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-ActiveOpens.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::tcpmib.ActiveOpens
probe::tcpmib.ActiveOpens
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.ActiveOpens — \n Count an active opening of a socket\n-

Synopsis

tcpmib.ActiveOpens

Values

sk

\n- pointer to the struct sock being acted on\n-

op

\n+

Synopsis

tcpmib.ActiveOpens

Values

op

\n value to be added to the counter (default value of 1)\n+

sk

\n+ pointer to the struct sock being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n tcpmib_filter_key. If the packet passes the filter is is\n counted in the global ActiveOpens (equivalent to SNMP's MIB\n TCP_MIB_ACTIVEOPENS)\n

Prev Up Next
probe::linuxmib.TCPMemoryPressures Home probe::tcpmib.AttemptFails
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-EstabResets.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-EstabResets.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::tcpmib.EstabResets
probe::tcpmib.EstabResets
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.EstabResets — \n Count the reset of a socket\n-

Synopsis

tcpmib.EstabResets

Values

op

\n- value to be added to the counter (default value of 1)\n-

sk

\n+

Synopsis

tcpmib.EstabResets

Values

sk

\n pointer to the struct sock being acted on\n+

op

\n+ value to be added to the counter (default value of 1)\n

Description

\n The packet pointed to by skb is filtered by the function\n tcpmib_filter_key. If the packet passes the filter is is\n counted in the global EstabResets (equivalent to SNMP's MIB\n TCP_MIB_ESTABRESETS)\n

Prev Up Next
probe::tcpmib.CurrEstab Home probe::tcpmib.InSegs
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-InSegs.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-InSegs.html", "unified_diff": "@@ -1,13 +1,13 @@\n probe::tcpmib.InSegs
probe::tcpmib.InSegs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.InSegs — \n Count an incoming tcp segment\n-

Synopsis

tcpmib.InSegs

Values

op

\n- value to be added to the counter (default value of 1)\n-

sk

\n+

Synopsis

tcpmib.InSegs

Values

sk

\n pointer to the struct sock being acted on\n+

op

\n+ value to be added to the counter (default value of 1)\n

Description

\n The packet pointed to by skb is filtered by the function\n tcpmib_filter_key (or ipmib_filter_key for tcp v4).\n If the packet passes the filter is is\n counted in the global InSegs (equivalent to SNMP's MIB\n TCP_MIB_INSEGS)\n

Prev Up Next
probe::tcpmib.EstabResets Home probe::tcpmib.OutRsts
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-OutSegs.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-OutSegs.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::tcpmib.OutSegs
probe::tcpmib.OutSegs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.OutSegs — \n Count the sending of a TCP segment\n-

Synopsis

tcpmib.OutSegs

Values

sk

\n- pointer to the struct sock being acted on\n-

op

\n+

Synopsis

tcpmib.OutSegs

Values

op

\n value to be added to the counter (default value of 1)\n+

sk

\n+ pointer to the struct sock being acted on\n

Description

\n The packet pointed to by skb is filtered by the function\n tcpmib_filter_key. If the packet passes the filter is is\n counted in the global OutSegs (equivalent to SNMP's MIB\n TCP_MIB_OUTSEGS)\n

Prev Up Next
probe::tcpmib.OutRsts Home probe::tcpmib.PassiveOpens
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-init.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-init.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::tty.init
probe::tty.init
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.init — \n Called when a tty is being initalized\n-

Synopsis

tty.init

Values

module

\n- the module name\n-

driver_name

\n+

Synopsis

tty.init

Values

driver_name

\n the driver name\n+

module

\n+ the module name\n

name

\n the driver .dev_name name\n

Prev Up Next
Chapter 11. TTY Tapset Home probe::tty.ioctl
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-ioctl.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-ioctl.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::tty.ioctl
probe::tty.ioctl
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.ioctl — \n called when a ioctl is request to the tty\n-

Synopsis

tty.ioctl

Values

name

\n- the file name\n-

arg

\n+

Synopsis

tty.ioctl

Values

arg

\n the ioctl argument\n

cmd

\n the ioctl command\n+

name

\n+ the file name\n

Prev Up Next
probe::tty.init Home probe::tty.open
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-open.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-open.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::tty.open
probe::tty.open
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.open — \n Called when a tty is opened\n-

Synopsis

tty.open

Values

file_flags

\n+

Synopsis

tty.open

Values

file_mode

\n+ the file mode\n+

inode_state

\n+ the inode state\n+

file_flags

\n the file flags\n

inode_number

\n the inode number\n-

inode_state

\n- the inode state\n

file_name

\n the file name\n-

file_mode

\n- the file mode\n

inode_flags

\n the inode flags\n

Prev Up Next
probe::tty.ioctl Home probe::tty.poll
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-read.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-read.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,11 +1,11 @@\n probe::tty.read
probe::tty.read
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.read — \n called when a tty line will be read\n

Synopsis

tty.read

Values

buffer

\n the buffer that will receive the characters\n+

file_name

\n+ the file name lreated to the tty\n

nr

\n The amount of characters to be read\n

driver_name

\n the driver name\n-

file_name

\n- the file name lreated to the tty\n

Prev Up Next
probe::tty.poll Home probe::tty.receive
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-receive.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-receive.html", "unified_diff": "@@ -1,17 +1,17 @@\n probe::tty.receive
probe::tty.receive
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.receive — \n called when a tty receives a message\n-

Synopsis

tty.receive

Values

cp

\n- the buffer that was received\n-

name

\n- the name of the module file\n+

Synopsis

tty.receive

Values

count

\n+ The amount of characters received\n

driver_name

\n the driver name\n+

fp

\n+ The flag buffer\n

id

\n the tty id\n-

count

\n- The amount of characters received\n

index

\n The tty Index\n-

fp

\n- The flag buffer\n+

cp

\n+ the buffer that was received\n+

name

\n+ the name of the module file\n

Prev Up Next
probe::tty.read Home probe::tty.register
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-register.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-register.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::tty.register
probe::tty.register
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.register — \n Called when a tty device is registred\n-

Synopsis

tty.register

Values

index

\n- the tty index requested\n+

Synopsis

tty.register

Values

name

\n+ the driver .dev_name name\n

module

\n the module name\n+

index

\n+ the tty index requested\n

driver_name

\n the driver name\n-

name

\n- the driver .dev_name name\n

Prev Up Next
probe::tty.receive Home probe::tty.release
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-release.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-release.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::tty.release
probe::tty.release
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.release — \n Called when the tty is closed\n-

Synopsis

tty.release

Values

file_mode

\n- the file mode\n-

inode_flags

\n+

Synopsis

tty.release

Values

inode_flags

\n the inode flags\n

file_name

\n the file name\n-

inode_state

\n- the inode state\n

inode_number

\n the inode number\n

file_flags

\n the file flags\n+

inode_state

\n+ the inode state\n+

file_mode

\n+ the file mode\n

Prev Up Next
probe::tty.register Home probe::tty.resize
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-resize.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-resize.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::tty.resize
probe::tty.resize
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.resize — \n Called when a terminal resize happens\n-

Synopsis

tty.resize

Values

new_xpixel

\n- the new xpixel value\n-

old_xpixel

\n- the old xpixel\n-

old_ypixel

\n- the old ypixel\n-

old_col

\n- the old col value\n-

new_ypixel

\n+

Synopsis

tty.resize

Values

new_ypixel

\n the new ypixel value\n-

new_col

\n- the new col value\n

old_row

\n the old row value\n

name

\n the tty name\n+

new_xpixel

\n+ the new xpixel value\n+

old_col

\n+ the old col value\n+

new_col

\n+ the new col value\n+

old_xpixel

\n+ the old xpixel\n+

old_ypixel

\n+ the old ypixel\n

new_row

\n the new row value\n

Prev Up Next
probe::tty.release Home probe::tty.unregister
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-unregister.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-unregister.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::tty.unregister
probe::tty.unregister
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.unregister — \n Called when a tty device is being unregistered\n-

Synopsis

tty.unregister

Values

name

\n- the driver .dev_name name\n-

driver_name

\n+

Synopsis

tty.unregister

Values

driver_name

\n the driver name\n-

module

\n- the module name\n

index

\n the tty index requested\n+

module

\n+ the module name\n+

name

\n+ the driver .dev_name name\n

Prev Up Next
probe::tty.resize Home probe::tty.write
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-tty-write.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-tty-write.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,11 +1,11 @@\n probe::tty.write
probe::tty.write
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.write — \n write to the tty line\n

Synopsis

tty.write

Values

driver_name

\n the driver name\n-

nr

\n- The amount of characters\n

file_name

\n the file name lreated to the tty\n+

nr

\n+ The amount of characters\n

buffer

\n the buffer that will be written\n

Prev Up Next
probe::tty.unregister Home Chapter 12. Interrupt Request (IRQ) Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect-return.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::udp.disconnect.return
probe::udp.disconnect.return
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.disconnect.return — \n UDP has been disconnected successfully\n-

Synopsis

udp.disconnect.return

Values

family

\n+

Synopsis

udp.disconnect.return

Values

daddr

\n+ A string representing the destination IP address\n+

ret

\n+ Error code (0: no error) \n+

family

\n IP address family\n-

name

\n- The name of this probe\n

sport

\n UDP source port\n-

daddr

\n- A string representing the destination IP address\n-

saddr

\n- A string representing the source IP address\n+

name

\n+ The name of this probe\n

dport

\n UDP destination port\n-

ret

\n- Error code (0: no error) \n+

saddr

\n+ A string representing the source IP address\n

Context

\n The process which requested a UDP disconnection\n

Prev Up Next
probe::udp.disconnect Home probe::udp.recvmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::udp.disconnect
probe::udp.disconnect
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.disconnect — \n Fires when a process requests for a UDP disconnection\n-

Synopsis

udp.disconnect

Values

dport

\n+

Synopsis

udp.disconnect

Values

flags

\n+ Flags (e.g. FIN, etc) \n+

dport

\n UDP destination port\n

sock

\n Network socket used by the process\n+

name

\n+ The name of this probe\n

saddr

\n A string representing the source IP address\n-

flags

\n- Flags (e.g. FIN, etc) \n

daddr

\n A string representing the destination IP address\n

family

\n IP address family\n-

name

\n- The name of this probe\n

sport

\n UDP source port\n

Context

\n The process which requests a UDP disconnection \n

Prev Up Next
probe::tcp.setsockopt.return Home probe::udp.disconnect.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg-return.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::udp.recvmsg.return
probe::udp.recvmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.recvmsg.return — \n Fires whenever an attempt to receive a UDP message received is completed\n-

Synopsis

udp.recvmsg.return

Values

dport

\n- UDP destination port\n-

size

\n- Number of bytes received by the process\n-

daddr

\n- A string representing the destination IP address\n-

saddr

\n+

Synopsis

udp.recvmsg.return

Values

saddr

\n A string representing the source IP address\n-

family

\n- IP address family\n

name

\n The name of this probe\n+

dport

\n+ UDP destination port\n+

size

\n+ Number of bytes received by the process\n

sport

\n UDP source port\n+

family

\n+ IP address family\n+

daddr

\n+ A string representing the destination IP address\n

Context

\n The process which received a UDP message\n

Prev Up Next
probe::udp.recvmsg Home probe::udp.sendmsg
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::udp.recvmsg
probe::udp.recvmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.recvmsg — \n Fires whenever a UDP message is received\n-

Synopsis

udp.recvmsg

Values

dport

\n- UDP destination port\n-

size

\n- Number of bytes received by the process\n+

Synopsis

udp.recvmsg

Values

family

\n+ IP address family\n+

sport

\n+ UDP source port\n

daddr

\n A string representing the destination IP address\n-

sock

\n- Network socket used by the process\n

saddr

\n A string representing the source IP address\n-

family

\n- IP address family\n

name

\n The name of this probe\n-

sport

\n- UDP source port\n+

dport

\n+ UDP destination port\n+

size

\n+ Number of bytes received by the process\n+

sock

\n+ Network socket used by the process\n

Context

\n The process which received a UDP message\n

Prev Up Next
probe::udp.disconnect.return Home probe::udp.recvmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-sendmsg-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-sendmsg-return.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::udp.sendmsg.return
probe::udp.sendmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.sendmsg.return — \n Fires whenever an attempt to send a UDP message is completed\n-

Synopsis

udp.sendmsg.return

Values

size

\n- Number of bytes sent by the process\n-

name

\n+

Synopsis

udp.sendmsg.return

Values

name

\n The name of this probe\n+

size

\n+ Number of bytes sent by the process\n

Context

\n The process which sent a UDP message\n

Prev Up Next
probe::udp.sendmsg Home Chapter 14. Socket Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-udp-sendmsg.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-udp-sendmsg.html", "unified_diff": "@@ -1,21 +1,21 @@\n probe::udp.sendmsg
probe::udp.sendmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.sendmsg — \n Fires whenever a process sends a UDP message\n-

Synopsis

udp.sendmsg

Values

dport

\n- UDP destination port\n+

Synopsis

udp.sendmsg

Values

family

\n+ IP address family\n+

sport

\n+ UDP source port\n

daddr

\n A string representing the destination IP address\n-

size

\n- Number of bytes sent by the process\n-

family

\n- IP address family\n

saddr

\n A string representing the source IP address\n+

dport

\n+ UDP destination port\n+

size

\n+ Number of bytes sent by the process\n

sock

\n Network socket used by the process \n-

sport

\n- UDP source port\n

name

\n The name of this probe\n

Context

\n The process which sent a UDP message \n

Prev Up Next
probe::udp.recvmsg.return Home probe::udp.sendmsg.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc-node.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc-node.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::vm.kmalloc_node
probe::vm.kmalloc_node
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmalloc_node — \n Fires when kmalloc_node is requested\n-

Synopsis

vm.kmalloc_node

Values

gfp_flag_name

\n- type of kmemory to allocate(in string format)\n-

bytes_alloc

\n- allocated Bytes\n-

call_site

\n- address of the function caling this kmemory function\n-

gfp_flags

\n- type of kmemory to allocate\n+

Synopsis

vm.kmalloc_node

Values

caller_function

\n+ name of the caller function\n

bytes_req

\n requested Bytes\n-

caller_function

\n- name of the caller function\n

ptr

\n pointer to the kmemory allocated\n+

gfp_flag_name

\n+ type of kmemory to allocate(in string format)\n

name

\n name of the probe point\n+

gfp_flags

\n+ type of kmemory to allocate\n+

bytes_alloc

\n+ allocated Bytes\n+

call_site

\n+ address of the function caling this kmemory function\n

Prev Up Next
probe::vm.kmalloc Home probe::vm.kmem_cache_alloc
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::vm.kmalloc
probe::vm.kmalloc
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmalloc — \n Fires when kmalloc is requested\n-

Synopsis

vm.kmalloc

Values

call_site

\n+

Synopsis

vm.kmalloc

Values

caller_function

\n+ name of the caller function\n+

bytes_req

\n+ requested Bytes\n+

gfp_flags

\n+ type of kmemory to allocate\n+

bytes_alloc

\n+ allocated Bytes\n+

call_site

\n address of the kmemory function\n+

ptr

\n+ pointer to the kmemory allocated\n

gfp_flag_name

\n type of kmemory to allocate (in String format)\n-

bytes_alloc

\n- allocated Bytes\n-

gfp_flags

\n- type of kmemory to allocate\n-

bytes_req

\n- requested Bytes\n-

caller_function

\n- name of the caller function\n

name

\n name of the probe point\n-

ptr

\n- pointer to the kmemory allocated\n

Prev Up Next
probe::vm.kfree Home probe::vm.kmalloc_node
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc-node.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc-node.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::vm.kmem_cache_alloc_node
probe::vm.kmem_cache_alloc_node
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_alloc_node — \n Fires when kmem_cache_alloc_node is requested\n-

Synopsis

vm.kmem_cache_alloc_node

Values

gfp_flag_name

\n+

Synopsis

vm.kmem_cache_alloc_node

Values

name

\n+ name of the probe point\n+

gfp_flag_name

\n type of kmemory to allocate(in string format)\n-

bytes_alloc

\n- allocated Bytes\n+

ptr

\n+ pointer to the kmemory allocated\n

call_site

\n address of the function calling this kmemory function\n+

bytes_alloc

\n+ allocated Bytes\n

gfp_flags

\n type of kmemory to allocate\n-

bytes_req

\n- requested Bytes\n

caller_function

\n name of the caller function\n-

name

\n- name of the probe point\n-

ptr

\n- pointer to the kmemory allocated\n+

bytes_req

\n+ requested Bytes\n

Prev Up Next
probe::vm.kmem_cache_alloc Home probe::vm.kmem_cache_free
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc.html", "unified_diff": "@@ -1,19 +1,19 @@\n probe::vm.kmem_cache_alloc
probe::vm.kmem_cache_alloc
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_alloc — \n Fires when kmem_cache_alloc is requested\n-

Synopsis

vm.kmem_cache_alloc

Values

call_site

\n- address of the function calling this kmemory function.\n+

Synopsis

vm.kmem_cache_alloc

Values

ptr

\n+ pointer to the kmemory allocated\n

gfp_flag_name

\n type of kmemory to allocate(in string format)\n+

name

\n+ name of the probe point\n

bytes_alloc

\n allocated Bytes\n

gfp_flags

\n type of kmemory to allocate\n+

call_site

\n+ address of the function calling this kmemory function.\n

bytes_req

\n requested Bytes\n

caller_function

\n name of the caller function.\n-

ptr

\n- pointer to the kmemory allocated\n-

name

\n- name of the probe point\n

Prev Up Next
probe::vm.kmalloc_node Home probe::vm.kmem_cache_alloc_node
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-free.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-free.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -1,11 +1,11 @@\n probe::vm.kmem_cache_free
probe::vm.kmem_cache_free
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_free — \n Fires when kmem_cache_free is requested\n

Synopsis

vm.kmem_cache_free

Values

call_site

\n Address of the function calling this kmemory function\n-

caller_function

\n- Name of the caller function.\n-

name

\n- Name of the probe point\n

ptr

\n Pointer to the kmemory allocated which is returned by kmem_cache\n+

name

\n+ Name of the probe point\n+

caller_function

\n+ Name of the caller function.\n

Prev Up Next
probe::vm.kmem_cache_alloc_node Home probe::vm.mmap
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-mmap.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-mmap.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::vm.mmap
probe::vm.mmap
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.mmap — \n Fires when an mmap is requested\n-

Synopsis

vm.mmap

Values

address

\n+

Synopsis

vm.mmap

Values

length

\n+ the length of the memory segment \n+

address

\n the requested address\n

name

\n name of the probe point\n-

length

\n- the length of the memory segment \n

Context

\n The process calling mmap.\n

Prev Up Next
probe::vm.kmem_cache_free Home probe::vm.munmap
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault-return.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault-return.html", "unified_diff": "@@ -1,11 +1,11 @@\n probe::vm.pagefault.return
probe::vm.pagefault.return
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.pagefault.return — \n Indicates what type of fault occurred\n-

Synopsis

vm.pagefault.return

Values

fault_type

\n+

Synopsis

vm.pagefault.return

Values

name

\n+ name of the probe point\n+

fault_type

\n returns either \n 0 (VM_FAULT_OOM) for out of memory faults, \n 2 (VM_FAULT_MINOR) for minor faults, 3 (VM_FAULT_MAJOR) for \n major faults, or 1 (VM_FAULT_SIGBUS) if the fault was neither OOM, minor fault, \n nor major fault.\n-

name

\n- name of the probe point\n

Prev Up Next
probe::vm.pagefault Home probe::vm.write_shared
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault.html", "unified_diff": "@@ -1,12 +1,12 @@\n probe::vm.pagefault
probe::vm.pagefault
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.pagefault — \n Records that a page fault occurred\n-

Synopsis

vm.pagefault

Values

write_access

\n- indicates whether this was a write or read access; 1 indicates a write, \n- while 0 indicates a read\n-

name

\n+

Synopsis

vm.pagefault

Values

name

\n name of the probe point\n

address

\n the address of the faulting memory access; i.e. the address that caused the page fault\n+

write_access

\n+ indicates whether this was a write or read access; 1 indicates a write, \n+ while 0 indicates a read\n

Context

\n The process which triggered the fault\n

Prev Up Next
probe::vm.oom_kill Home probe::vm.pagefault.return
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-vm-write-shared-copy.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-vm-write-shared-copy.html", "unified_diff": "@@ -1,15 +1,15 @@\n probe::vm.write_shared_copy
probe::vm.write_shared_copy
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.write_shared_copy — \n Page copy for shared page write\n-

Synopsis

vm.write_shared_copy

Values

name

\n- Name of the probe point\n-

address

\n- The address of the shared write\n-

zero

\n+

Synopsis

vm.write_shared_copy

Values

zero

\n boolean indicating whether it is a zero page\n (can do a clear instead of a copy)\n+

address

\n+ The address of the shared write\n+

name

\n+ Name of the probe point\n

Context

\n The process attempting the write.\n

Description

\n Fires when a write to a shared page requires a page copy. This is\n always preceded by a vm.write_shared.\n

Prev Up Next
probe::vm.write_shared Home Chapter 7. Task Time Tapset
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-workqueue-execute.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-workqueue-execute.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::workqueue.execute
probe::workqueue.execute
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::workqueue.execute — \n Executing deferred work\n-

Synopsis

workqueue.execute

Values

work_func

\n+

Synopsis

workqueue.execute

Values

work

\n+ work_struct* being executed\n+

work_func

\n pointer to handler function\n

wq_thread

\n task_struct of the workqueue thread\n-

work

\n- work_struct* being executed\n

Prev Up Next
probe::workqueue.destroy Home probe::workqueue.insert
\n"}, {"source1": "./usr/share/doc/systemtap-doc/tapsets/API-workqueue-insert.html", "source2": "./usr/share/doc/systemtap-doc/tapsets/API-workqueue-insert.html", "unified_diff": "@@ -1,9 +1,9 @@\n probe::workqueue.insert
probe::workqueue.insert
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::workqueue.insert — \n Queuing work on a workqueue\n-

Synopsis

workqueue.insert

Values

work_func

\n- pointer to handler function\n-

work

\n+

Synopsis

workqueue.insert

Values

work

\n work_struct* being queued\n

wq_thread

\n task_struct of the workqueue thread\n+

work_func

\n+ pointer to handler function\n

Prev Up Next
probe::workqueue.execute Home Chapter 13. Networking Tapset
\n"}]}]}]}]}