From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: rafael.tinoco@linaro.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] tst_umount: Retry open() after umount to handle delayed device release
Date: Mon, 11 Aug 2025 16:20:41 +0200 [thread overview]
Message-ID: <aJn8ObtEEaAf1H-a@yuki.lan> (raw)
In-Reply-To: <CAEemH2dFjv2Mn-CfM6HEZxT7BR45PAHuwQcMa6dckxemf0tvzg@mail.gmail.com>
Hi!
> From the bpfstrace logs, there seems udisksd listening to the same
> udevevents and probes the device via libblockdev/blkid, performing
> real O_RDONLY opens (flags=0x0). These O_RDONLY opens from
> udisksd race with mkfs.ext3’s O_EXCL open, intermittently causing
> “apparently in use by the system” (EBUSY).
>
> Does this analysis sound reasonable to you?
Yes. So we have another daemon that probes block devices on each change.
I suppose that turning off udisksd fixes the problem right? If that is
so I would be inclined just to print a message to turn off udisksd if
mkfs on a loop device fails...
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-08-11 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 16:33 [LTP] lib: tst_device.c - /dev/loop0 in use Rafael David Tinoco
2019-01-02 13:19 ` Cyril Hrubis
2025-08-06 7:44 ` [LTP] [PATCH] tst_umount: Retry open() after umount to handle delayed device release Li Wang via ltp
2025-08-06 9:27 ` Cyril Hrubis
2025-08-11 12:42 ` Li Wang via ltp
2025-08-11 14:20 ` Cyril Hrubis [this message]
2025-08-12 3:43 ` Li Wang via ltp
2025-08-12 11:17 ` Cyril Hrubis
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=aJn8ObtEEaAf1H-a@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=rafael.tinoco@linaro.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