ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a1fb441c84
Spdk/test/nvmf/target/fabrics_fuzz.sh

40 lines
1.6 KiB
Bash
Raw Normal View History

test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
#!/usr/bin/env bash
add (c) and SPDX header to bash files as needed per Intel policy to include file commit date using git cmd below. The policy does not apply to non-Intel (C) notices. git log --follow -C90% --format=%ad --date default <file> | tail -1 and then pull just the year from the result. Intel copyrights were not added to files where Intel either had no contribution ot the contribution lacked substance (ie license header updates, formatting changes, etc) For intel copyrights added, --follow and -C95% were used. Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: I2ef86976095b88a9bf5b1003e59f3943cd6bbe4c Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15209 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2022-11-02 15:49:40 +00:00
# SPDX-License-Identifier: BSD-3-Clause
# Copyright (C) 2018 Intel Corporation
# All rights reserved.
#
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
testdir=$(readlink -f $(dirname $0))
rootdir=$(readlink -f $testdir/../../..)
source $rootdir/test/common/autotest_common.sh
source $rootdir/test/nvmf/common.sh
nvmftestinit
test: use single core when testing nvme fuzz with nvmf target There's really no need to specify 4 cores for both the fuzz app and the nvmf target, since only one is ever used. Reducing the mask to a single core each makes the fuzz.sh tests easier to run in VMs with a limited number of cores. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id956ac8d0d7f75cb0e76b78c9175b4aa520218bf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9725 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-10-04 22:44:05 +00:00
"${NVMF_APP[@]}" -m 0x1 > $output_dir/nvmf_fuzz_tgt_output.txt 2>&1 &
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
nvmfpid=$!
nvme_fuzz: pass trid on command line only Previously the Transport IDs would need to be an ini-style config file that the nvme_fuzz app would then parse. Instead just add a -F option that tells the nvme_fuzz app which subsystem(s) to fuzz. This simplifies the fuzz_app code a bit and makes it a bit easier to use. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I622f5173ff36e15d653155c4eb7eaaecb5564818 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9603 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-09-23 16:25:49 +00:00
trap 'process_shm --id $NVMF_APP_SHM_ID; killprocess $nvmfpid; nvmftestfini $1; exit 1' SIGINT SIGTERM EXIT
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
waitforlisten $nvmfpid
test/nvmf: add NVMF_TRANSPORT_OPTS global For a lot of the tests, we may want to specify different options for each transport. I believe this will be more prevalent as we add more transport specific options. Change-Id: I83a915629460d1d869eaba4bc86822d7563402ac Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/461740 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-07-15 04:42:41 +00:00
$rpc_py nvmf_create_transport $NVMF_TRANSPORT_OPTS -u 8192
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
scripts/rpc: Change rpc construct_malloc_bdev to bdev_malloc_create This is patch that implements changes according to proposal submitted in https://review.gerrithub.io/c/spdk/spdk/+/453036 Change-Id: I5423cd34cb5fc111b34cab2b7f7c6c5f11898af8 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/464677 Reviewed-by: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-08-09 11:15:35 +00:00
$rpc_py bdev_malloc_create -b Malloc0 64 512
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
RPC: rename nvmf_subsystem_create to nvmf_create_subsystem Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Ic3aa9f168b2e612e461c450ef1e5e1ae81fa5635 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468963 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-09-20 10:22:44 +00:00
$rpc_py nvmf_create_subsystem nqn.2016-06.io.spdk:cnode1 -a -s SPDK00000000000001
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
$rpc_py nvmf_subsystem_add_ns nqn.2016-06.io.spdk:cnode1 Malloc0
$rpc_py nvmf_subsystem_add_listener nqn.2016-06.io.spdk:cnode1 -t $TEST_TRANSPORT -a $NVMF_FIRST_TARGET_IP -s $NVMF_PORT
nvme_fuzz: pass trid on command line only Previously the Transport IDs would need to be an ini-style config file that the nvme_fuzz app would then parse. Instead just add a -F option that tells the nvme_fuzz app which subsystem(s) to fuzz. This simplifies the fuzz_app code a bit and makes it a bit easier to use. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I622f5173ff36e15d653155c4eb7eaaecb5564818 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9603 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-09-23 16:25:49 +00:00
trid="trtype:$TEST_TRANSPORT adrfam:IPv4 subnqn:nqn.2016-06.io.spdk:cnode1 traddr:$NVMF_FIRST_TARGET_IP trsvcid:$NVMF_PORT"
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
# Note that we chose a consistent seed to ensure that this test is consistent in nightly builds.
test: use single core when testing nvme fuzz with nvmf target There's really no need to specify 4 cores for both the fuzz app and the nvmf target, since only one is ever used. Reducing the mask to a single core each makes the fuzz.sh tests easier to run in VMs with a limited number of cores. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id956ac8d0d7f75cb0e76b78c9175b4aa520218bf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9725 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-10-04 22:44:05 +00:00
$rootdir/test/app/fuzz/nvme_fuzz/nvme_fuzz -m 0x2 -r "/var/tmp/nvme_fuzz" -t 30 -S 123456 -F "$trid" -N -a 2> $output_dir/nvmf_fuzz_logs1.txt
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
# We don't specify a seed for this test. Instead we run a static list of commands from example.json.
test: use single core when testing nvme fuzz with nvmf target There's really no need to specify 4 cores for both the fuzz app and the nvmf target, since only one is ever used. Reducing the mask to a single core each makes the fuzz.sh tests easier to run in VMs with a limited number of cores. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Id956ac8d0d7f75cb0e76b78c9175b4aa520218bf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9725 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-10-04 22:44:05 +00:00
$rootdir/test/app/fuzz/nvme_fuzz/nvme_fuzz -m 0x2 -r "/var/tmp/nvme_fuzz" -F "$trid" -j $rootdir/test/app/fuzz/nvme_fuzz/example.json -a 2> $output_dir/nvmf_fuzz_logs2.txt
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
RPC: rename delete_nvmf_subsystem to nvmf_delete_subsystem Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: I4654f254cae78b0def789b13754af7c70c73dabb Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/469111 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-09-23 10:17:30 +00:00
$rpc_py nvmf_delete_subsystem nqn.2016-06.io.spdk:cnode1
test/nvmf: add application for target fuzz testing. Enables us to test randomized data against the NVMe-oF target interface. Change-Id: Ie7ab46949ccd89f74b10b79a24256aeae2df89ab Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/431571 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Hailiang Wang <hailiangx.e.wang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: qun wan <qun.wan@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-10-31 21:53:50 +00:00
trap - SIGINT SIGTERM EXIT
nvmftestfini
test/nvmf: Remove redundant steps from fabrics_fuzz Also, clear generated fuzz logs upon successful test run - they may get quite big (> 250MB) in size which doesn't play well with the artifacts limit CI enforces. If the test succeeded then there's no point in keeping them around for any potential debugging. Signed-off-by: Michal Berger <michal.berger@intel.com> Change-Id: I240e8217cd50dba258310604c6985d8f6a832756 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15030 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2022-10-18 08:29:53 +00:00
rm "$output_dir/"nvmf_fuzz_logs*.txt
Reference in New Issue Copy Permalink