lkml.org 
[lkml]   [2003]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: sys/fs and sys/block
Patrick Mochel writes:
>

[...]

>
> >From the original author:
>
> "Also, struct kobject is embedded into struct super_block. It is
> naturally file system responsibility to register it (and may be some
> other kobject's) at mount, and unregister at umount."

I (the original author) think it is cleaner to leave initialization and
registering of this kobject to the file system back end. For example,
there is no obvious generic way to generate names for such objects, etc.

>
> I wonder if it can, and should, be done automatically. Or, if we can just
> use symlinks to point to the partitions, instead of creating a new object
> at all.

Err. Not sure I understand. kobject representing file system instance
would probably have completely different set of attributes than
underlying partition object. Then, there are !FS_REQUIRES_DEV file
systems.

>
> Thanks for the questions,
>

Nikita.

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

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.047 / U:1.672 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site