From: inbox1.sudheer@gmail.com (Sudheer Divakaran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How does the kernel chooses the 'vfat' module for fat32 partitions?
Date: Tue, 10 May 2011 10:18:42 +0530 [thread overview]
Message-ID: <BANLkTik9MFHGePPv2pdeHABMoCQPEExjDQ@mail.gmail.com> (raw)
Hi List,
I have one doubt regarding the component which determines that 'vfat'
module is the correct module to be used for accessing fat32 file
systems and how does vfat.ko became the ideal candidate for accessing
fat32 partition? For example, even though my /etc/fstab doesn't
contain any entry for my usbstick, which is having a fat32 partition,
when I issued the command 'mount /dev/sdb1 /mnt/usb' after inserting
the usbstick, I could see the following events in udevadm monitor
--kernel --udev' s output. Pls note the lines
"KERNEL[1304999552.510965] add /module/fat (module)
KERNEL[1304999552.516633] add /module/vfat (module)"
[Questions]
1. Who makes the decision that vfat.ko is to be used for fat32
partitions? Is it kernel/udev or some other component?
2. How does the kernel or the module loader determines that 'vfat' is
the correct module to be used for accessing fat32 partition? AFAIK,
there is nothing similar to 'MODULE_DEVICE_TABLE' in vfat.ko's
sources, which maps partition type 'c' (partition type id for W95
FAT32) to vfat.ko (CMIIW) as in pci/usb drivers.
[udevadm monitor output]
KERNEL[1304999552.510965] add /module/fat (module)
KERNEL[1304999552.512169] add /kernel/slab/fat_cache (slab)
UDEV [1304999552.512212] add /module/fat (module)
KERNEL[1304999552.512239] add /kernel/slab/fat_inode_cache (slab)
UDEV [1304999552.512263] add /kernel/slab/fat_cache (slab)
UDEV [1304999552.512289] add /kernel/slab/fat_inode_cache (slab)
KERNEL[1304999552.516633] add /module/vfat (module)
UDEV [1304999552.516861] add /module/vfat (module)
KERNEL[1304999552.542026] add /module/nls_cp437 (module)
UDEV [1304999552.542267] add /module/nls_cp437 (module)
KERNEL[1304999552.545320] add /module/nls_iso8859_1 (module)
UDEV [1304999552.545566] add /module/nls_iso8859_1 (module)
[more entries...]
TIA,
--
Thanks
Sudheer
next reply other threads:[~2011-05-10 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 4:48 Sudheer Divakaran [this message]
2011-05-10 6:40 ` How does the kernel chooses the 'vfat' module for fat32 partitions? Mulyadi Santosa
2011-05-10 7:08 ` Sudheer Divakaran
2011-05-10 7:47 ` Sudheer Divakaran
2011-05-10 14:35 ` Mulyadi Santosa
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=BANLkTik9MFHGePPv2pdeHABMoCQPEExjDQ@mail.gmail.com \
--to=inbox1.sudheer@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).