All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	arjanv@redhat.com, dwmw2@infradead.org, jmorris@redhat.com,
	chrisw@osdl.org, sfrench@samba.org, mike@halcrow.us,
	trond.myklebust@fys.uio.no, mrmacman_g4@mac.com
Subject: Re: [PATCH] implement in-kernel keys & keyring management
Date: Mon, 9 Aug 2004 13:27:23 -0700	[thread overview]
Message-ID: <20040809202723.GA31794@kroah.com> (raw)
In-Reply-To: <15760.1092043400@redhat.com>

On Mon, Aug 09, 2004 at 10:23:20AM +0100, David Howells wrote:
> 
> Greg KH <greg@kroah.com> wrote:
> > I think that if the /proc interface was moved over to sysfs (which is
> > where it should be), a number of these syscalls would go away.
> 
> Well, I could move these two files into /sysfs. But just doing that wouldn't
> get rid of any of the system calls. To move these files into sysfs, should I
> create a "keys" subsystem?

Yes.  But then you would have to split the info in these files up into
many different files, as it's "one value per file" for sysfs files :)

> Can you elaborate as to what you envision? I wonder if you'd thinking that I
> should make every key a kobject and fan-out them out in a directory in sysfs
> somewhere. I really don't want to do that, though... kobject seems to add
> quite a large overhead that I'd rather avoid (a directory in sysfs for
> instance).

James has gone into the detail of a filesystem type interface for this
code much better than I can envision.

thanks,

greg k-h

  reply	other threads:[~2004-08-09 20:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07  0:31 [PATCH] implement in-kernel keys & keyring management David Howells
2004-08-07  8:17 ` Andrew Morton
2004-08-07 16:33   ` [PATCH] implement in-kernel keys & keyring management [try #2] David Howells
2004-08-07 17:48     ` [PATCH] implement in-kernel keys & keyring management [try #3] David Howells
2004-08-08  4:45     ` [PATCH] implement in-kernel keys & keyring management [try #2] James Morris
2004-08-09  9:33       ` David Howells
2004-08-09 14:08         ` James Morris
2004-08-09 14:35           ` David Howells
2004-08-09 15:47             ` James Morris
2004-08-10 18:49               ` David Howells
2004-08-08  2:52   ` [PATCH] implement in-kernel keys & keyring management Greg KH
2004-08-09  9:23     ` David Howells
2004-08-09 20:27       ` Greg KH [this message]
2004-08-07  8:59 ` Trond Myklebust
2004-08-07 17:45   ` David Howells
2004-08-08  5:14 ` James Morris
2004-08-08  5:25   ` Linus Torvalds
2004-08-09  1:14     ` James Morris
2004-08-09  4:27       ` Linus Torvalds
2004-08-09  6:32         ` bert hubert
2004-08-09 10:16         ` David Howells
2004-08-09 14:51         ` Alan Cox
2004-08-09 10:01       ` David Howells
2004-08-09  9:45     ` David Howells
2004-08-09 15:24       ` [PATCH] implement in-kernel keys & keyring management [try #4] David Howells
2004-08-09 21:13         ` Kyle Moffett
2004-08-10 17:59       ` [PATCH] implement in-kernel keys & keyring management [try #5] David Howells
2004-08-11  6:37         ` Chris Wright
2004-08-11  9:46           ` David Howells
2004-08-11 12:34         ` [PATCH] implement in-kernel keys & keyring management [try #6] David Howells
2004-08-11 19:10           ` [PATCH] keys & keyring management: key filesystem David Howells
2004-08-09  9:40   ` [PATCH] implement in-kernel keys & keyring management David Howells
     [not found] <200410191615.i9JGF8IW002712@hera.kernel.org>
2004-10-20 12:52 ` Arjan van de Ven

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=20040809202723.GA31794@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=chrisw@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@halcrow.us \
    --cc=mrmacman_g4@mac.com \
    --cc=sfrench@samba.org \
    --cc=torvalds@osdl.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.