mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Patrick Mochel <mochel@osdl.org>
Cc: Dominik Brodowski <linux@brodo.de>, <linux-kernel@vger.kernel.org>
Subject: Re: sys/fs and sys/block
Date: Fri, 7 Mar 2003 15:02:49 +0300	[thread overview]
Message-ID: <15976.35433.135732.310826@laputa.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0303051035100.994-100000@localhost.localdomain>

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

      reply	other threads:[~2003-03-07 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  8:39 Dominik Brodowski
2003-03-05 17:05 ` Patrick Mochel
2003-03-07 12:02   ` Nikita Danilov [this message]

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=15976.35433.135732.310826@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=mochel@osdl.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

all inboxes | Powered by JetHome®