Re: [PATCH 0/9] overlay filesystem: request for inclusion (v17)

[Sedat Dilek]

On Wed, Mar 13, 2013 at 8:58 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Mar 13, 2013 at 12:54 PM, Eric W. Biederman
> <ebiederm@xxxxxxxxxxxx> wrote:
>>>
>>> Hehe, I just checked my new kernel... that does not work (nothing in the logs).
>>> But I think it's good to see if the filesystem is registered/loaded.
>>
>> lsmod | grep overlayfs
>
> How about the compiled-in case? What's wrong with just using the
> obvious /proc/filesystems?
>

As I don't need OverlayFS in my daily life, I have it here built as a module.

Nevertheless, as module or built-in /me as an end-user wants to know
what's going on.
So, dmesg is normally my first weapon.

I grep-ed trrough a bit through all the filesystems in fs/ and it is
not handled unique.

"Loaded" BTW is not the right term in FS-folks-jargon: The functions
are called (un)register_filesystem().

$ dmesg | grep -i loaded
[    0.241037] vgaarb: loaded
[    0.241243] libata version 3.00 loaded.
[    0.358574] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 252)
[    0.368711] brd: module loaded
[    0.369832] loop: module loaded
[    0.650086] PM: Hibernation image not present or could not be loaded.
[    0.651150] Loaded X.509 cert 'Magrathea: Glacier signing key:
e75e3a59e59cb48db975ac12e21a905289ada56f'
[    1.788947] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    8.617549] lp: driver loaded but no devices found
[   10.490721] wmi: Mapper loaded
[   11.994985] iwlwifi 0000:01:00.0: loaded firmware version 18.168.6.1
[   73.885056] squashfs: loaded
[   81.345070] overlayfs: loaded

I am not sure whether those lines "blabla: module loaded" is true for
loop (block) it is a hardcoded printk-line.
I doubt...

CONFIG_BLK_DEV_LOOP=y

Last but not least, user-space apps like GRUB trigger fs loaded.
For me this is helpful.
You might be bored or whatever reason I can't or don't want to understand.

And just to have some fun about status informations:
Check your drm (kms) driver with date and version :-).
Stuff that is not maintained should be thrown out (yes, I had sent patches...).

- Sedat -

>              Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/