From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and sysfs permissions
Date: Fri, 27 May 2005 16:39:06 +0000 [thread overview]
Message-ID: <9e4733910505270939a2fb262@mail.gmail.com> (raw)
In-Reply-To: <9e47339105051915025188e535@mail.gmail.com>
On 5/27/05, Maneesh Soni <maneesh@in.ibm.com> wrote:
> It should be doable. But again this will increase the size of sysfs_dirent
> structure. If I am not wrong we will need to save (persistent) struct iattr
> for each sysfs_dirent there by increasing its size by 52 bytes on i386 and
> we will need ->i_op->setattr() and ->i_op->getattr() routines for sysfs.
Could the 52 byte allocation be deferred until someone actually
changes the sysfs attributes? Most attributes won't get changed.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-05-27 16:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 22:02 udev and sysfs permissions Jon Smirl
2005-05-19 22:10 ` Kay Sievers
2005-05-20 4:33 ` Greg KH
2005-05-20 14:06 ` Jon Smirl
2005-05-20 18:33 ` Greg KH
2005-05-20 21:11 ` Jon Smirl
2005-05-20 21:26 ` Jon Smirl
2005-05-20 21:27 ` Greg KH
2005-05-20 21:40 ` Jon Smirl
2005-05-20 21:40 ` Greg KH
2005-05-20 21:41 ` Jon Smirl
2005-05-20 21:53 ` Jon Smirl
2005-05-20 21:54 ` Greg KH
2005-05-20 21:56 ` Greg KH
2005-05-20 22:07 ` Kay Sievers
2005-05-20 22:09 ` Greg KH
2005-05-26 23:09 ` Greg KH
2005-05-27 12:44 ` Maneesh Soni
2005-05-27 16:39 ` Jon Smirl [this message]
2005-05-27 21:51 ` Greg KH
2005-05-28 5:06 ` maneesh
2005-05-28 5:08 ` maneesh
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=9e4733910505270939a2fb262@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-hotplug@vger.kernel.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 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.