From: Greg KH <greg@kroah.com>
To: Michal Ludvig <michal@logix.cz>
Cc: James Morris <jmorris@redhat.com>,
Andreas Happe <andreashappe@flatline.ath.cx>,
cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org
Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs
Date: Tue, 7 Sep 2004 09:52:48 -0700 [thread overview]
Message-ID: <20040907165248.GC8530@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0409071845101.19015@maxipes.logix.cz>
On Tue, Sep 07, 2004 at 06:47:06PM +0200, Michal Ludvig wrote:
> On Tue, 7 Sep 2004, James Morris wrote:
>
> > On Sun, 5 Sep 2004, Greg KH wrote:
> >
> > > Other than that, I like this move, /proc/crypto isn't the best thing to
> > > have in a proc filesystem :)
> >
> > The only issue is what to do about potentially expanding this into an API
> > (e.g. open() an algorithm and write to it). Does this sort of thing
> > belong in sysfs?
>
> I already proposed to have a 'cryptoapifs' mounted e.g. under
> /dev/cryptoapi with the "active" entrypoints while /sys would only hold
> the "status" of the cryptoapi. Would this be a better approach?
That sounds acceptable.
thanks,
greg k-h
next prev parent reply other threads:[~2004-09-07 17:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040831175449.GA2946@final-judgement.ath.cx>
[not found] ` <Xine.LNX.4.44.0409010043020.30561-100000@thoron.boston.redhat.com>
2004-09-01 8:28 ` [cryptoapi/sysfs] display cipher details in sysfs Andreas Happe
2004-09-06 0:04 ` Greg KH
2004-09-07 16:37 ` James Morris
2004-09-07 16:45 ` Greg KH
2004-09-07 16:47 ` Michal Ludvig
2004-09-07 16:52 ` Greg KH [this message]
2004-09-06 18:49 ` Michal Ludvig
2004-09-07 14:35 ` Andreas Happe
2004-09-07 15:49 ` Michal Ludvig
2004-09-07 16:57 ` Andreas Happe
2004-09-10 11:21 ` Andreas Happe
2004-09-10 10:55 ` Andreas Happe
2004-09-27 8:41 ` Andreas Happe
2004-09-27 9:10 ` Michal Ludvig
2004-09-28 12:34 ` Andreas Happe
2004-09-29 9:36 ` Andreas Happe
2004-09-29 9:37 ` Andreas Happe
2004-09-29 14:13 ` Michal Ludvig
2004-09-29 13:13 ` Michal Ludvig
2004-09-27 15:53 ` James Morris
2004-09-28 12:21 ` [PATCH 2.6.9-rc2 1/2] cryptoapi: update sysfs-patch Andreas Happe
2004-09-28 12:23 ` [PATCH 2.6.9-rc2 2/2] cryptoapi: make /proc/crypto optional Andreas Happe
2004-09-28 14:32 ` Sven Schuster
2004-09-29 8:40 ` Andreas Happe
2004-09-07 16:36 ` [cryptoapi/sysfs] display cipher details in sysfs James Morris
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=20040907165248.GC8530@kroah.com \
--to=greg@kroah.com \
--cc=andreashappe@flatline.ath.cx \
--cc=cryptoapi@lists.logix.cz \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.cz \
/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.