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, 19 Oct 2005 14:55:45 -0500 [thread overview]
Message-ID: <afcef88a0510191255t47047d1q93b4a7428609b324@mail.gmail.com> (raw)
In-Reply-To: <1129750686.29319.7.camel@polarbear.fsl.cs.sunysb.edu>
On 10/19/05, Charles P. Wright <cwright@cs.sunysb.edu> wrote:
> The reference count of an eCryptfs dentry may not be the same as the
> reference count of the lower-level dentry. If the eCryptfs dentry hits
> zero, but the lower-level dentry does not, you are going to remove the
> lower-level dentry from the name space prematurely.
>
> This manifested itself on Unionfs running over squashfs.
I C, if you will. Now that I know, consider it removed :)
> > > In ecryptfs_llseek, If you are adding pages for extra information, you
> > > need to convert the offset to a lower-level offset, and then convert the
> > > return back to what user space expects it to be. You should test fsx on
> > > your file system, to sort these types of things out.
> > I believe that this is working, we have run fsx "succesfully" for
> > 10000 iterations. However, its not a total success because we are
> > bugging out in fs/buffer.c:1822 BUG_ON(PageWriteback(page));
> > Will look a bit more closely though.
> Actually nevermind, you are using generic_file_llseek on your own file
> instead of passing the operation down. That should be fine and dandy
> for files, but I don't know if you are going to have problems with
> directories.
Guess I'll have to test a bit more then... *marks on the TODO*.
Would you like to take a stab at why we are hitting the
fs/buffer.c:1822 BUG_ON(PageWriteback(page)); problem?
I'm pretty much at a loss, although, I will be honest, I haven't
looked into it very much
(it's scary).
Thanks for the help,
Mike
next prev parent reply other threads:[~2005-10-19 19:55 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 [this message]
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
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=afcef88a0510191255t47047d1q93b4a7428609b324@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).