From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, torvalds@osdl.org, hch@infradead.org,
viro@ftp.linux.org.uk, linux-fsdevel@vger.kernel.org,
penberg@cs.helsinki.fi, ezk@cs.sunysb.edu, mhalcrow@us.ibm.com
Subject: [PATCH 0 of 2] Stackfs: generic stackable filesystem helper functions
Date: Fri, 13 Oct 2006 07:18:48 -0400 [thread overview]
Message-ID: <patchbomb.1160738328@thor.fsl.cs.sunysb.edu> (raw)
The following patches introduce stackfs_copy_* functions. These functions
copy inode attributes (such as {a,c,m}time, mode, etc.) from one inode to
another.
While, intended for stackable filesystems any portion of the kernel wishing
to copy inode attributes can use them.
This series consists of two patches, the first introduces the stackfs
functions, and the second makes eCryptfs a user.
Signed-off-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
4 files changed, 85 insertions(+), 59 deletions(-)
fs/ecryptfs/file.c | 3 +
fs/ecryptfs/inode.c | 71 +++++++++-------------------------------------
fs/ecryptfs/main.c | 5 +--
include/linux/stack_fs.h | 65 ++++++++++++++++++++++++++++++++++++++++++
next reply other threads:[~2006-10-13 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 11:18 Josef Jeff Sipek [this message]
2006-10-13 11:18 ` [PATCH 1 of 2] Stackfs: Introduce stackfs_copy_{attr,inode}_* Josef Jeff Sipek
2006-10-13 19:04 ` Andrew James Wade
2006-10-15 17:38 ` [PATCH] " Jan Engelhardt
2006-10-13 19:27 ` Andrew Morton
2006-10-13 20:07 ` Josef Sipek
2006-10-13 20:16 ` Josef Sipek
2006-10-13 20:37 ` Andrew Morton
2006-10-15 12:36 ` Jan Engelhardt
2006-10-13 11:18 ` [PATCH 2 of 2] eCryptfs: Use stackfs's generic copy inode attr functions Josef Jeff Sipek
2006-10-13 12:02 ` [PATCH 0 of 2] Stackfs: generic stackable filesystem helper functions Pekka Enberg
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=patchbomb.1160738328@thor.fsl.cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@osdl.org \
--cc=ezk@cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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).