Linux block layer
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Jan Kara <jack@suse.cz>
Cc: "osandov@fb.com" <osandov@fb.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] blktests: Ignore errors from wait(1)
Date: Wed, 15 Jun 2022 11:50:14 +0000	[thread overview]
Message-ID: <20220615115014.nm3utxgvq2hkhuzo@shindev> (raw)
In-Reply-To: <20220614131803.hwoykpwzfh6pxmda@quack3.lan>

On Jun 14, 2022 / 15:18, Jan Kara wrote:
> On Tue 14-06-22 07:04:54, Shinichiro Kawasaki wrote:

[...]

> Yes, I suspect it depends on the shell as well (because otherwise I expect
> people would hit this much earlier than me :). The bash I have is
> "4.4.23(1)-release" - the one in openSUSE 15.3 and it shows the error
> pretty reliably...

I guess the problematic wait command output is job exit status report. To
confirm my guess, could your share example of the wait command output?

Based on my guess, I checked difference between bash 4.4 and my bash 5.1, but I
did not find notable bash code change about job exit status report. Hmm.

Your patch covers several waits in the block group. I suspect other waits in
other groups may have same risk. Instead of your patch, could you try the patch
below on your system? If it works, all waits in all groups can be addressed.

diff --git a/check b/check
index 7037d88..ac24afa 100755
--- a/check
+++ b/check
@@ -440,6 +440,10 @@ _run_test() {
 	RUN_FOR_ZONED=0
 	FALLBACK_DEVICE=0
 
+	# Ensure job control monitor mode is off in this sub-shell to suppress
+	# job status output.
+	set +m
+
 	# shellcheck disable=SC1090
 	. "tests/${TEST_NAME}"
 


-- 
Shin'ichiro Kawasaki

  reply	other threads:[~2022-06-15 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 15:17 [PATCH] blktests: Ignore errors from wait(1) Jan Kara
2022-06-13 22:48 ` Chaitanya Kulkarni
2022-06-14 13:15   ` Jan Kara
2022-06-15 11:30     ` Shinichiro Kawasaki
2022-06-14  7:04 ` Shinichiro Kawasaki
2022-06-14 13:18   ` Jan Kara
2022-06-15 11:50     ` Shinichiro Kawasaki [this message]
2022-06-15 16:56       ` Jan Kara
2022-06-16  4:16         ` Shinichiro Kawasaki

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=20220615115014.nm3utxgvq2hkhuzo@shindev \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.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