From: Ming Lei <ming.lei@redhat.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Omar Sandoval <osandov@osandov.com>,
Omar Sandoval <osandov@fb.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH blktests] block/002: delay debugfs directory check
Date: Wed, 20 Apr 2022 17:34:05 +0800 [thread overview]
Message-ID: <Yl/TjWYle8mOOwlO@T590> (raw)
In-Reply-To: <20220420045911.914393-1-shinichiro.kawasaki@wdc.com>
On Wed, Apr 20, 2022 at 01:59:11PM +0900, Shin'ichiro Kawasaki wrote:
> The test case block/002 checks that device removal during blktrace run
> does not leak debugfs directory. The Linux kernel commit 0a9a25ca7843
> ("block: let blkcg_gq grab request queue's refcnt") triggered failure of
> the test case. The commit delayed queue release and debugfs directory
> removal then the test case checks directory existence too early. To
> avoid this false-positive failure, delay the directory existence check.
>
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
> tests/block/002 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/block/002 b/tests/block/002
> index 9b183e7..8061c91 100755
> --- a/tests/block/002
> +++ b/tests/block/002
> @@ -29,6 +29,7 @@ test() {
> echo "debugfs directory deleted with blktrace active"
> fi
> { kill $!; wait; } >/dev/null 2>/dev/null
> + sleep 0.5
> if [[ -d /sys/kernel/debug/block/${SCSI_DEBUG_DEVICES[0]} ]]; then
> echo "debugfs directory leaked"
> fi
Hello,
Jens has merged Yu Kuai's fix[1], so I think it won't be triggered now.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=block-5.18&id=a87c29e1a85e64b28445bb1e80505230bf2e3b4b
Thanks,
Ming
next prev parent reply other threads:[~2022-04-20 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:59 [PATCH blktests] block/002: delay debugfs directory check Shin'ichiro Kawasaki
2022-04-20 7:46 ` Johannes Thumshirn
2022-04-20 9:34 ` Ming Lei [this message]
2022-04-20 12:42 ` Shinichiro Kawasaki
2022-04-20 15:05 ` Ming Lei
2022-04-20 22:44 ` Jens Axboe
2022-04-21 0:02 ` Shinichiro Kawasaki
2022-04-21 8:38 ` Ming Lei
2022-04-21 12:04 ` Shinichiro Kawasaki
2022-04-21 8:51 ` yukuai (C)
2022-04-21 9:30 ` Ming Lei
2022-04-21 11:14 ` yukuai (C)
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=Yl/TjWYle8mOOwlO@T590 \
--to=ming.lei@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox