All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halcrow <mhalcrow@us.ibm.com>
To: akpm@osdl.org
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-mm2 & ecryptfs
Date: Mon, 26 Jun 2006 17:30:32 -0500	[thread overview]
Message-ID: <20060626223032.GD2867@us.ibm.com> (raw)
In-Reply-To: <1151359559.32250.15.camel@dyn9047017100.beaverton.ibm.com>

On Mon, Jun 26, 2006 at 03:05:59PM -0700, Badari Pulavarty wrote:
> I am not sure, if its already reported or not. 
> 
> 2.6.17-mm2 vfs_statfs() takes a "dentry" instead of "sb".
> ecryptfs seems to be broken :(

Yeah, that one slipped right by me with the API change.

---

Update ecryptfs_statfs (API change).

Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>

---
 fs/ecryptfs/super.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

b3c064b2248bd949c07900aab9ac4517f301d66c
diff --git a/fs/ecryptfs/super.c b/fs/ecryptfs/super.c
index 437a542..8b014a4 100644
--- a/fs/ecryptfs/super.c
+++ b/fs/ecryptfs/super.c
@@ -122,9 +122,9 @@ static void ecryptfs_put_super(struct su
  * Get the filesystem statistics. Currently, we let this pass right through
  * to the lower filesystem and take no action ourselves.
  */
-static inline int ecryptfs_statfs(struct super_block *sb, struct kstatfs *buf)
+static inline int ecryptfs_statfs(struct dentry *dentry, struct kstatfs *buf)
 {
-	return vfs_statfs(ecryptfs_superblock_to_lower(sb), buf);
+	return vfs_statfs(ecryptfs_dentry_to_lower(dentry), buf);
 }
 
 /**
-- 
1.3.3


      reply	other threads:[~2006-06-26 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 22:05 2.6.17-mm2 & ecryptfs Badari Pulavarty
2006-06-26 22:30 ` Michael Halcrow [this message]

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=20060626223032.GD2867@us.ibm.com \
    --to=mhalcrow@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /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.