c9c7c281f8
Part of #2256 * achieve * additionally * against * aliases * already * another * arguments * between * capabilities * comparison * compatibility * configuration * continuing * controlq * cpumask * default * depends * dereferenced * discussed * dissect * driver * environment * everything * excluded * existing * expectation * failed * fails * following * functions * hugepages * identifiers * implicitly * in_capsule * increment * initialization * initiator * integrity * iteration * latencies * libraries * management * namespace * negotiated * negotiation * nonexistent * number * occur * occurred * occurring * offsetting * operations * outstanding * overwhelmed * parameter * parameters * partition * preempts * provisioned * responded * segment * skipped * struct * subsystem * success * successfully * sufficiently * this * threshold * transfer * transferred * unchanged * unexpected * unregistered * useless * utility * value * variable * workload Change-Id: I21ca7dab4ef575b5767e50aaeabc34314ab13396 Signed-off-by: Josh Soref <jsoref@gmail.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10409 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# Overview
|
|
|
|
This application is intended to fuzz test the iSCSI target by submitting
|
|
randomized PDU commands through a simulated iSCSI initiator.
|
|
|
|
## Input
|
|
|
|
1. iSCSI initiator send a login request PDU to iSCSI Target. Once a session is connected,
|
|
2. iSCSI initiator send huge amount and random PDUs continuously to iSCSI Target.
|
|
3. iSCSI initiator send a logout request PDU to iSCSI Target in the end.
|
|
|
|
Especially, iSCSI initiator need to build different bhs according to different bhs opcode.
|
|
Then iSCSI initiator will receive all kinds of response opcodes from iSCSI Target.
|
|
The application will terminate when run time expires (see the -t flag).
|
|
|
|
## Output
|
|
|
|
By default, the fuzzer will print commands that:
|
|
|
|
1. Complete successfully back from the target, or
|
|
2. Are outstanding at the time of a connection error occurs.
|
|
|
|
Commands are dumped as named objects in json format which can then be supplied back to the
|
|
script for targeted debugging on a subsequent run.
|
|
|
|
At the end of each test run, a summary is printed in the following format:
|
|
|
|
~~~bash
|
|
device 0x11c3b90 stats: Sent 1543 valid opcode PDUs, 16215 invalid opcode PDUs.
|
|
~~~
|