From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v2 2/2] block/033: add test to cover gendisk leak
Date: Fri, 17 Feb 2023 14:21:06 +0000 [thread overview]
Message-ID: <20230217142106.yisjzahdgfxd3ddz@shindev> (raw)
In-Reply-To: <20230217013851.1402864-3-ming.lei@redhat.com>
On Feb 17, 2023 / 09:38, Ming Lei wrote:
> So far only sync ublk removal is supported, and the device's
> last reference is dropped in gendisk's ->free_disk(), so it
> can be used to test gendisk leak issue.
>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> common/ublk | 34 ++++++++++++++++++++++++++++++++++
> tests/block/033 | 40 ++++++++++++++++++++++++++++++++++++++++
> tests/block/033.out | 2 ++
> 3 files changed, 76 insertions(+)
> create mode 100644 common/ublk
> create mode 100755 tests/block/033
> create mode 100644 tests/block/033.out
>
> diff --git a/common/ublk b/common/ublk
> new file mode 100644
> index 0000000..a7b442a
> --- /dev/null
> +++ b/common/ublk
> @@ -0,0 +1,34 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-3.0+
> +# Copyright (C) 2023 Ming Lei
> +#
> +# ublk_drv helper functions.
> +
> +. common/shellcheck
> +
> +_have_ublk() {
> + _have_driver ublk_drv
> + _have_src_program ublk/miniublk
> +}
> +
> +_remove_ublk_devices() {
> + src/ublk/miniublk del -a
> +}
> +
> +_init_ublk() {
> + _remove_ublk_devices
> +
> + if ! modprobe -r ublk_drv || ! modprobe ublk_drv; then
When ublk_drv is built as a built-in module, modprobe -r fails and prints out an
error. I suggest to modify the line above as follows:
modprobe -rq ublk_drv
if ! modprobe ublk_drv; then
With this, I confirmed that the test case can be run with built-in ublk_drv.
I suggest to remove the word "modular" in the message below.
> + SKIP_REASONS+=("requires modular ublk_drv")
> + return 1
> + fi
> +
> + udevadm settle
> + return 0
> +}
> +
> +_exit_ublk() {
> + _remove_ublk_devices
> + udevadm settle
> + modprobe -r -q ublk_drv
> +}
> diff --git a/tests/block/033 b/tests/block/033
> new file mode 100755
> index 0000000..eaba599
> --- /dev/null
> +++ b/tests/block/033
> @@ -0,0 +1,40 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-3.0+
> +# Copyright (C) 2023 Ming Lei
> +#
> +# Test if gendisk is leaked, and regression in the following commit
> +# c43332fe028c ("blk-cgroup: delay calling blkcg_exit_disk until disk_release")
> +# can be covered
> +
> +. tests/block/rc
> +. common/ublk
> +
> +DESCRIPTION="add & delete ublk device and test if gendisk is leaked"
> +QUICK=1
> +
> +requires() {
> + _have_ublk
> +}
> +
> +test() {
> + local ublk_prog="src/ublk/miniublk"
> +
> + echo "Running ${TEST_NAME}"
> +
> + if ! _init_ublk; then
> + return 1
> + fi
> +
> + ${ublk_prog} add -t null -n 0 --quiet > /dev/null 2>&1
> + if ! ${ublk_prog} list -n 0 > /dev/null 2>&1; then
> + echo "fail to list dev"
> + fi
When I repeated to run this test case, I often observed failure. The dd below
reported an error: "failed to open '/dev/ublkb0': No such file or directory". I
added "udevadm settle" here, then the failure disappeared.
> + if ! dd if=/dev/ublkb0 iflag=direct of=/dev/null bs=1M count=512 > /dev/null 2>&1; then
> + echo "fail io"
> + fi
> + ${ublk_prog} del -n 0 > /dev/null 2>&1
The outputs of ${ublk_prog} and dd are all redirected to /dev/null, so it was a
bit difficult for me to debug the error. I suggest to redirect and append to
"$FULL" instead.
> +
> + _exit_ublk
> +
> + echo "Test complete"
> +}
> diff --git a/tests/block/033.out b/tests/block/033.out
> new file mode 100644
> index 0000000..067846a
> --- /dev/null
> +++ b/tests/block/033.out
> @@ -0,0 +1,2 @@
> +Running block/033
> +Test complete
> --
> 2.31.1
>
--
Shin'ichiro Kawasaki
prev parent reply other threads:[~2023-02-17 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 1:38 [PATCH blktests v2 0/2] blktests: add mini ublk source and blktests/033 Ming Lei
2023-02-17 1:38 ` [PATCH blktests v2 1/2] src: add mini ublk source code Ming Lei
2023-02-17 1:42 ` Ming Lei
2023-02-17 14:05 ` Shinichiro Kawasaki
2023-02-20 3:13 ` Ming Lei
2023-02-17 1:38 ` [PATCH blktests v2 2/2] block/033: add test to cover gendisk leak Ming Lei
2023-02-17 14:21 ` Shinichiro Kawasaki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230217142106.yisjzahdgfxd3ddz@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.