From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <util-linux@vger.kernel.org>
Subject: udev + libbklid: synchronized uevent handling between kernel and ueventd?
Date: Mon, 7 Jul 2014 12:09:51 +0800 [thread overview]
Message-ID: <53BA1D8F.9060907@cn.fujitsu.com> (raw)
Hi,
If I understand right, when kernel sends a KOBJ_CHANGE uevent, udevd
catches it and
update the ctime/mtime of the device file in /dev according to the uevent.
Do I understand the procedure right?
Then a problem occurs to me that, the above procedure is asynchronized,
so sometimes concurreny may happen when kernel send the uevent but udev has
not yet updated the ctime/mtime of device file, making libblkid cache
still valid and gives wrong result.
(bringing the old thread again:
http://www.spinics.net/lists/util-linux-ng/msg09154.html)
So i'm wondering is there some synchronized method to send uevent and
wait for it completed?
Currently I use a method that opens and updates ctime/mtime in kernel
spaces, but it's somewhat
ugly.
Hope there will be some elegent method.
Thanks,
Qu
reply other threads:[~2014-07-07 4:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53BA1D8F.9060907@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=util-linux@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 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.