7c2524b8eb
MD032 - Lists should be surrounded by blank lines Fixed all errors Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Idd18d38386c0150f5d68068a59717a34d4e1d991 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9142 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| iscsi_fuzz.c | ||
| Makefile | ||
| README.md | ||
Overview
This application is intended to fuzz test the iSCSI target by submitting randomized PDU commands through a simulated iSCSI initiator.
Input
- iSCSI initiator send a login request PDU to iSCSI Target. Once a session is connected,
- iSCSI initiator send huge amount and random PDUs continuously to iSCSI Target.
- 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 responsed 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:
- Complete successfully back from the target, or
- 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:
device 0x11c3b90 stats: Sent 1543 valid opcode PDUs, 16215 invalid opcode PDUs.