ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5efa3d61ff
Spdk/test/app/fuzz/iscsi_fuzz
History
Tomasz Zawadzki 2172c432cf log: simplify SPDK_LOG_REGISTER_COMPONENT 
This patch removes the string from register component.
Removed are all instances in libs or hardcoded in apps.

Starting with this patch literal passed to register,
serves as name for the flag.

All instances of SPDK_LOG_* were replaced with just *
in lowercase.
No actual name change for flags occur in this patch.

Affected are SPDK_LOG_REGISTER_COMPONENT() and
SPDK_*LOG() macros.

Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Change-Id: I002b232fde57ecf9c6777726b181fc0341f1bb17
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4495
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Mellanox Build Bot
Reviewed-by: Anil Veerabhadrappa <anil.veerabhadrappa@broadcom.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Community-CI: Broadcom CI
2020-10-14 08:00:35 +00:00
..
.gitignore test/iscsi: add application for target fuzz testing. 2020-03-13 08:53:46 +00:00
iscsi_fuzz.c log: simplify SPDK_LOG_REGISTER_COMPONENT 2020-10-14 08:00:35 +00:00
Makefile test/iscsi: add application for target fuzz testing. 2020-03-13 08:53:46 +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.