From: Zorro Lang <zlang@kernel.org>
To: David Disseldorp <ddiss@suse.de>
Cc: fstests@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v2] common/rc: add default _udev_wait timeout
Date: Sat, 16 May 2026 00:31:31 +0800 [thread overview]
Message-ID: <agdKGqbpc8VABCmi@zlang-mailbox> (raw)
In-Reply-To: <20260323044557.2668-2-ddiss@suse.de>
On Mon, Mar 23, 2026 at 03:45:58PM +1100, David Disseldorp wrote:
> If udevd isn't running then "udevadm wait" loops endlessly. With a
> --timeout parameter provided, udevadm (udev-254.27) prints to stderr:
> Timed out for waiting devices being initialized.
>
> The error message causes test failure via golden output mismatch and
> is easier to debug than an infinite loop.
>
> The timeout parameter is also compatible with existing
> args="--removed <dev>" callers. 60 seconds is relatively arbitrary, but
> should be long enough to avoid premature timeout on regular systems.
>
> Signed-off-by: David Disseldorp <ddiss@suse.de>
> ---
> Changes since v1:
> - increase timeout from 10 to 60 seconds
>
> common/rc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/common/rc b/common/rc
> index fd4ca964..a490893f 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -5544,7 +5544,7 @@ _udev_wait()
> if [ -z "$UDEV_WAIT_PROG" ]; then
> $UDEV_SETTLE_PROG >/dev/null 2>&1
> else
> - $UDEV_WAIT_PROG $args
> + $UDEV_WAIT_PROG --timeout 60 $args
60s is good to me. As there's not more review points from others, let's
have this change.
Reviewed-by: Zorro Lang <zlang@kernel.org>
> fi
> }
>
> --
> 2.51.0
>
>
prev parent reply other threads:[~2026-05-15 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 4:45 [PATCH v2] common/rc: add default _udev_wait timeout David Disseldorp
2026-05-15 16:31 ` Zorro Lang [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=agdKGqbpc8VABCmi@zlang-mailbox \
--to=zlang@kernel.org \
--cc=david@fromorbit.com \
--cc=ddiss@suse.de \
--cc=fstests@vger.kernel.org \
/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