From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Phillip Hellewell <phillip@hellewell.homeip.net>
Cc: linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 2/3] eCryptfs: export key type
Date: Fri, 3 Jun 2005 15:03:39 -0500 [thread overview]
Message-ID: <20050603200339.GA2445@halcrow.us> (raw)
In-Reply-To: <20050602054852.GB4514@sshock.rn.byu.edu>
On Wed, Jun 01, 2005 at 11:48:52PM -0600, Phillip Hellewell wrote:
> This is the second in a series of three patches for the eCryptfs
> kernel module.
>
> The key_type_user symbol in user_defined.c needs to be exported.
> ...
> +EXPORT_SYMBOL( key_type_user );
This is the only modification necessary to support eCryptfs. While we
are working on getting it ready for merging into the mainline kernel,
we would like to distribute it as a separate kernel module, and we
would like for users or distro's do not need to modify their kernels
to build and run it.
Would there be any objections to exporting the key_type_user symbol?
Is there any general reason why kernel modules should not have access
to the user key type struct?
Mike
next prev parent reply other threads:[~2005-06-03 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 5:48 [PATCH 2/3] eCryptfs: export key type Phillip Hellewell
2005-06-03 20:03 ` Michael Halcrow [this message]
2005-06-06 9:42 ` David Howells
2005-06-06 18:42 ` [PATCH 2/3, 2.6.12-rc5-mm1] eCryptfs: export user " Michael Halcrow
2005-06-07 9:52 ` David Howells
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=20050603200339.GA2445@halcrow.us \
--to=mhalcrow@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@hellewell.homeip.net \
/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