All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RFC: Attributes in /sys/cdev
Date: Fri, 19 Sep 2003 19:47:12 -0700	[thread overview]
Message-ID: <20030920024712.GA9387@kroah.com> (raw)
In-Reply-To: <20030920012844.GD7665@parcelfarce.linux.theplanet.co.uk>

On Sat, Sep 20, 2003 at 02:28:44AM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> 
> BTW, I suspect that we need a way to say "this kobject and its children
> will *never* have any attributes and will never be seen in sysfs".  There
> are quite a few uses when we keep kobject as a refcounting vehicle, etc.,
> but have nothing meaningful to show in sysfs tree.  Keep in mind that
> sysfs nodes (including attributes) are not free - it's struct inode +
> struct dentry at the very least.  Both pinned down and permanently mapped...

Hm, I've used them this way by just calling kobject_init, kobject_get
and kobject_put.  As long as you never call kobject_register or
kobject_add, the sysfs hookups never happen.

Is that what you are looking for?  

thanks,

greg k-h

  reply	other threads:[~2003-09-20  2:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 23:10 [PATCH] RFC: Attributes in /sys/cdev Jonathan Corbet
2003-09-19 23:32 ` Greg KH
2003-09-20  1:28 ` viro
2003-09-20  2:47   ` Greg KH [this message]
2003-09-22 16:29   ` Patrick Mochel
2003-09-22 16:46   ` Jonathan Corbet
2003-09-22 21:00     ` viro
2003-09-22 21:15       ` Jonathan Corbet
2003-09-22 22:37         ` viro
2003-09-24 22:22           ` Greg KH

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=20030920024712.GA9387@kroah.com \
    --to=greg@kroah.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.