public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Phillip Hellewell <phillip@hellewell.homeip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] eCryptfs: eCryptfs kernel module
Date: Thu, 2 Jun 2005 00:33:03 -0700	[thread overview]
Message-ID: <20050602073303.GA9373@kroah.com> (raw)
In-Reply-To: <20050602054740.GA4514@sshock.rn.byu.edu>

On Wed, Jun 01, 2005 at 11:47:40PM -0600, Phillip Hellewell wrote:
> 
> While eCryptfs is functional, there is a significant amount of work
> yet to be done; a perusal of the source will reveal that there is a
> lot of low-hanging fruit/trivial fixes (David Howells: we promise that
> using your keyring correctly is near the top of the list, right after
> we get these memory leaks resolved).  It derives from cryptfs, which
> is a cryptographic filesystem instantiated by Erez Zadok's stackable
> filesystem framework, FiST.  We are aware that there are some extant
> bugs in the version of cryptfs that we built off of; as those are made
> known, we will be applying fixes.  In the meantime, we would like the
> eCryptfs kernel module to be merged into the mainline kernel.

Why not fix up the stuff that you know needs to be fixed?  It should not
be merged until then at the least.

Good luck,

greg k-h

  reply	other threads:[~2005-06-02  7:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  5:47 [PATCH 1/3] eCryptfs: eCryptfs kernel module Phillip Hellewell
2005-06-02  7:33 ` Greg KH [this message]
2005-06-02  7:33   ` James Morris
2005-06-02 12:32     ` Michael Halcrow
2005-06-02 14:51       ` Greg KH
2005-06-02 12:28   ` Michael Halcrow
2005-06-02 14:52     ` Greg KH
2005-06-02 16:33     ` 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=20050602073303.GA9373@kroah.com \
    --to=greg@kroah.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