From: Steffen Sledz <sledz@dresearch-fe.de>
To: linux-hotplug@vger.kernel.org
Subject: When does the kernel emits add events?
Date: Mon, 15 Aug 2011 11:09:05 +0000 [thread overview]
Message-ID: <4E48FE51.4060706@dresearch-fe.de> (raw)
Hi udev-Team,
just a short question for my understanding. When does the kernel emits add events for block devices?
With 'udevadm monitor' i've seen something that is confusing me:
1. I've an unmounted vfat partition. After running 'fsck.vfat -a /dev/sdb1' an add event occurs, but not after 'fsck.vfat -V /dev/sdb1'?
2. We have an embedded device based on an OXE810 platform. When loading the related kernel module the kernel emits an add event for the disk itself (e.g. /dev/sdb) and for all partitions on it (/dev/sdb1, ...). But then the kernel continues to send add events for the disk itself until *all* partitions on it are mounted. Is this an intended behaviour? Or a bug inside the kernel module?
Regards,
Steffen Sledz
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
reply other threads:[~2011-08-15 11:09 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=4E48FE51.4060706@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).