ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d16c5b49dd
Spdk/test/app/fuzz/iscsi_fuzz
History
Shuhei Matsumoto 6358538aa7 lib/iscsi: Pass the range (offset and length) to iscsi_conn_read_data_segment() 
This will make the current code simpler and make the following changes easier.

Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Change-Id: I5a06f7e876fee03ed05d880525b594f92cadcdca
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6410
Reviewed-by: Ziye Yang <ziye.yang@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
2021-02-23 08:52:20 +00:00
..
.gitignore test/iscsi: add application for target fuzz testing. 2020-03-13 08:53:46 +00:00
iscsi_fuzz.c lib/iscsi: Pass the range (offset and length) to iscsi_conn_read_data_segment() 2021-02-23 08:52:20 +00:00
Makefile build: use DEPDIRS variables to build SPDK_LIB_LIST 2020-12-18 09:40:01 +00:00
README.md test/iscsi: add README.md for iscsi fuzz testing 2020-04-06 07:56:07 +00:00

README.md

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 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:

  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:

device 0x11c3b90 stats: Sent 1543 valid opcode PDUs, 16215 invalid opcode PDUs.