From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, mhalcrow@us.ibm.com
Subject: [PATCH][-mm] fsstack: Fix up eCryptfs compilation
Date: Tue, 17 Oct 2006 18:39:35 -0400 [thread overview]
Message-ID: <20061017223935.GA2319@filer.fsl.cs.sunysb.edu> (raw)
From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
The fsstack tidy patch broke eCryptfs. This patch makes eCryptfs compile
again.
Signed-off-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
diff -r 2187c6b08f02 fs/ecryptfs/inode.c
--- a/fs/ecryptfs/inode.c Tue Oct 17 18:26:24 2006 -0400
+++ b/fs/ecryptfs/inode.c Tue Oct 17 18:29:43 2006 -0400
@@ -621,9 +621,9 @@ ecryptfs_rename(struct inode *old_dir, s
lower_new_dir_dentry->d_inode, lower_new_dentry);
if (rc)
goto out_lock;
- fsstack_copy_attr_all(new_dir, lower_new_dir_dentry->d_inode);
+ fsstack_copy_attr_all(new_dir, lower_new_dir_dentry->d_inode, NULL);
if (new_dir != old_dir)
- fsstack_copy_attr_all(old_dir, lower_old_dir_dentry->d_inode);
+ fsstack_copy_attr_all(old_dir, lower_old_dir_dentry->d_inode, NULL);
out_lock:
unlock_rename(lower_old_dir_dentry, lower_new_dir_dentry);
dput(lower_new_dentry);
@@ -908,7 +908,7 @@ static int ecryptfs_setattr(struct dentr
}
rc = notify_change(lower_dentry, ia);
out:
- fsstack_copy_attr_all(inode, lower_inode);
+ fsstack_copy_attr_all(inode, lower_inode, NULL);
return rc;
}
diff -r 2187c6b08f02 fs/ecryptfs/main.c
--- a/fs/ecryptfs/main.c Tue Oct 17 18:26:24 2006 -0400
+++ b/fs/ecryptfs/main.c Tue Oct 17 18:31:29 2006 -0400
@@ -116,7 +116,7 @@ int ecryptfs_interpose(struct dentry *lo
d_add(dentry, inode);
else
d_instantiate(dentry, inode);
- fsstack_copy_attr_all(inode, lower_inode);
+ fsstack_copy_attr_all(inode, lower_inode, NULL);
/* This size will be overwritten for real files w/ headers and
* other metadata */
fsstack_copy_inode_size(inode, lower_inode);
reply other threads:[~2006-10-17 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061017223935.GA2319@filer.fsl.cs.sunysb.edu \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®