linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Thompson <michael.craig.thompson@gmail.com>
To: "Charles P. Wright" <cwright@cs.sunysb.edu>
Cc: Michael Halcrow <mike@halcrow.us>, linux-fsdevel@vger.kernel.org
Subject: Re: eCryptfs: Request for review
Date: Wed, 26 Oct 2005 18:29:50 -0500	[thread overview]
Message-ID: <afcef88a0510261629i529c7ee5o3b39cc8ce1445252@mail.gmail.com> (raw)
In-Reply-To: <1129736164.25733.19.camel@polarbear.fsl.cs.sunysb.edu>

On 10/19/05, Charles P. Wright <cwright@cs.sunysb.edu> wrote:
> In inode.c:
> Instead of get_parent you can use dget_parent.  The core kernel just
> seems to have lock_parent as two lines in the function that need it
> instead of the function these days.
What function would that be? We've looked around to try to find out
what replaced it, but have had no luck :(

> For main.c, you can replace the nasty mount option string processing
> with lib/parser.c.
This is now taken care of, and yes, it is a lot nice :)

Thanks much,
Mike

  parent reply	other threads:[~2005-10-26 23:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:38 eCryptfs: Request for review Michael Halcrow
2005-10-18 19:59 ` Greg KH
2005-10-19 15:36 ` Charles P. Wright
2005-10-19 19:00   ` Michael Thompson
2005-10-19 19:38     ` Charles P. Wright
2005-10-19 19:55       ` Michael Thompson
2005-10-19 21:02         ` Erez Zadok
2005-10-19 21:38         ` Badari Pulavarty
2005-10-21 21:44           ` Michael Thompson
2005-10-21 21:56             ` Shaya Potter
2005-10-21 22:49             ` Badari Pulavarty
2005-10-24 18:19               ` Michael Thompson
2005-10-26 20:05                 ` Michael Thompson
2005-10-26 20:13                   ` Anton Altaparmakov
2005-10-27 13:13                     ` Charles P. Wright
2005-10-20 14:25         ` Charles P. Wright
2005-10-26 23:29   ` Michael Thompson [this message]
2005-10-27 13:12     ` Charles P. Wright

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=afcef88a0510261629i529c7ee5o3b39cc8ce1445252@mail.gmail.com \
    --to=michael.craig.thompson@gmail.com \
    --cc=cwright@cs.sunysb.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mike@halcrow.us \
    /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;
as well as URLs for NNTP newsgroup(s).