c556b6b892
Now that the trace library can handle multiple arguments, there's no point in passing 0 for tracepoints that don't have any arguments. This patch removes all such instances. It allows us to to verify that `spdk_trace_record()` was issued with the exact number of arguments as specified in the definition of the tracepoint. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Idbdb6f5111bd6175e145a12c1f0c095b62d744a9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8125 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ziye Yang <ziye.yang@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.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.