python/rpc: remove deprecated retry_count param

Remove deprecated retry_count parameter from
bdev_nvme_set_options rpc function

Change-Id: I1b415cfcfd7b3226d6331960ad42c500ba77f0aa
Signed-off-by: E

python/rpc: remove deprecated retry_count param

Remove deprecated retry_count parameter from
bdev_nvme_set_options rpc function

Change-Id: I1b415cfcfd7b3226d6331960ad42c500ba77f0aa
Signed-off-by: Eugene Kobyak <eugene.kobyak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23498
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Community-CI: Mellanox Build Bot

show more ...

llvm/nvmf: supress false memory leak of `qpair_ctx` and `ctrlr`

This behavior is only reproducible during fuzzing test, probably due
to asynchronous nature of `spdk_nvmf_qpair_disconnect` and
`nvmf_

llvm/nvmf: supress false memory leak of `qpair_ctx` and `ctrlr`

This behavior is only reproducible during fuzzing test, probably due
to asynchronous nature of `spdk_nvmf_qpair_disconnect` and
`nvmf_ctrlr_create`. It was verified that there is no real memory leak.

Fixes issue #3285.

Change-Id: I94129bb0cbb63e4d5f7c96ae856d0a398f812f33
Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/22713
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

test: remove unnecessary RPC address setting

Since most of the apps no longer attempt to start RPC server by default,
we no longer need to assign unique addresses.

Change-Id: I714e30268141efef6f911

test: remove unnecessary RPC address setting

Since most of the apps no longer attempt to start RPC server by default,
we no longer need to assign unique addresses.

Change-Id: I714e30268141efef6f9117d3d4e6dab04d4fdc50
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/22635
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <jim.harris@samsung.com>

show more ...

fuzzer: enable reporting address of leaked memory

This patch turns on reporting of the address of leaked
memory object, when a leak sanitizer is detecting a memory
leak during fuzz tests. This is do

fuzzer: enable reporting address of leaked memory

This patch turns on reporting of the address of leaked
memory object, when a leak sanitizer is detecting a memory
leak during fuzz tests. This is done by setting
LSAN_OPTIONS vaiable to 'report_objects=1'

Can be used to verify if the leaked object is really
a leak, or during memory leak debugging.
Example output:

Objects leaked above:
0x60700000a820 (72 bytes)

SUMMARY: AddressSanitizer: 72 byte(s) leaked in 1 allocation(s).

If 'report_objects' is not enabled, the address of leaked object
is not provided (only the size is reported)

Change-Id: I0d59ff82096b64ed17fb89e369b439c9f565f500
Signed-off-by: Marcin Spiewak <marcin.spiewak@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21896
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>

show more ...

fuzz/llvm: provide a prefix to use when saving artifacts

Save crash files and other artifacts in `$output_dir/llvm/`

Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Change-Id: I2

fuzz/llvm: provide a prefix to use when saving artifacts

Save crash files and other artifacts in `$output_dir/llvm/`

Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Change-Id: I2ff82b414592cc492b79c9178b7257b2e87440b5
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15827
Reviewed-by: Michal Berger <michal.berger@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

show more ...

llvm_nvme_fuzz: enable running llvm nvmf test in parallel

Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Change-Id: Iad129c1bc62116a93701a5f68c78351f01a4c878
Reviewed-on: https:/

llvm_nvme_fuzz: enable running llvm nvmf test in parallel

Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Change-Id: Iad129c1bc62116a93701a5f68c78351f01a4c878
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16249
Reviewed-by: Michal Berger <michal.berger@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

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% --forma

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>

show more ...

test/fuzz: write nvme fuzz test log to a file instead of on Console

The long time fuzz output size is so big that
cause Jenkins job abort.

Signed-off-by: Jun Wen <junx.wen@intel.com>
Change-Id: I5d

test/fuzz: write nvme fuzz test log to a file instead of on Console

The long time fuzz output size is so big that
cause Jenkins job abort.

Signed-off-by: Jun Wen <junx.wen@intel.com>
Change-Id: I5deeb1ff7414e2bf01cd3b5200e8c51d40487ad8
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15369
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: <qun.wan@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com>
Reviewed-by: Karol Latecki <karol.latecki@intel.com>

show more ...