From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, akpm@osdl.org, hch@infradead.org,
viro@ftp.linux.org.uk, mhalcrow@us.ibm.com,
chris.mason@oracle.com, ezk@cs.sunysb.edu,
penberg@cs.helsinki.fi, dm-devel@redhat.com, mingo@redhat.com,
reiserfs-dev@namesys.com
Subject: [PATCH 3 of 4] struct path: Move struct path from fs/namei.c into include/linux
Date: Wed, 18 Oct 2006 20:57:10 -0400 [thread overview]
Message-ID: <17ebaa342f0525a5f34e.1161219430@thor.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <patchbomb.1161219427@thor.fsl.cs.sunysb.edu>
From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
Moved struct path from fs/namei.c to include/linux/namei.h. This allows many
places in the VFS, as well as any stackable filesystem to easily keep track
of dentry-vfsmount pairs.
Signed-off-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
---
2 files changed, 5 insertions(+), 5 deletions(-)
fs/namei.c | 5 -----
include/linux/namei.h | 5 +++++
diff --git a/fs/namei.c b/fs/namei.c
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -569,11 +569,6 @@ fail:
path_release(nd);
return PTR_ERR(link);
}
-
-struct path {
- struct vfsmount *mnt;
- struct dentry *dentry;
-};
static inline void dput_path(struct path *path, struct nameidata *nd)
{
diff --git a/include/linux/namei.h b/include/linux/namei.h
--- a/include/linux/namei.h
+++ b/include/linux/namei.h
@@ -27,6 +27,11 @@ struct nameidata {
union {
struct open_intent open;
} intent;
+};
+
+struct path {
+ struct vfsmount *mnt;
+ struct dentry *dentry;
};
/*
next prev parent reply other threads:[~2006-10-19 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 0:57 [PATCH 0 of 4] fsstack: struct path Josef Jeff Sipek
2006-10-19 0:57 ` [PATCH 1 of 4] struct path: Rename Reiserfs's " Josef Jeff Sipek
2006-10-19 0:57 ` [PATCH 2 of 4] struct path: Rename DM's " Josef Jeff Sipek
2006-10-19 0:57 ` Josef Jeff Sipek [this message]
2006-10-19 0:57 ` [PATCH 4 of 4] struct path: make eCryptfs a user of " Josef Jeff Sipek
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=17ebaa342f0525a5f34e.1161219430@thor.fsl.cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@osdl.org \
--cc=chris.mason@oracle.com \
--cc=dm-devel@redhat.com \
--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=mingo@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=reiserfs-dev@namesys.com \
--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).