linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0 of 4] fsstack: struct path
Date: Wed, 18 Oct 2006 20:57:07 -0400	[thread overview]
Message-ID: <patchbomb.1161219427@thor.fsl.cs.sunysb.edu> (raw)

The following patches attempt to fix up the problems with 'struct path' as
discussed in the 'fsstack: struct path' thread on linux-kernel. The net
effect is moving struct path from fs/namei.c to include/linux/namei.h, as it
is quite useful (and it will discourage the (ab)use of struct nameidata.)

The fsstack code benefits from it as the stackable fs dentries have to keep
track of the lower dentry as well as the lower vfsmount.

The first two patches rename Reiserfs's 'struct path' to 'struct treepath',
and Device Mapper's 'struct path' to 'struct dm_path', respectively.

The third patch moves struct path from fs/namei.c to include/linux/namei.h,
making it accessible to any part of the VFS as well as other parts of the
kernel - stackable filesystem like eCryptfs and Unionfs come to mind.

The fourth patch converts eCryptfs's dentry-vfsmount pairs in the dentry
private data to struct path.

Signed-off-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>

             reply	other threads:[~2006-10-19  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19  0:57 Josef Jeff Sipek [this message]
2006-10-19  0:57 ` [PATCH 1 of 4] struct path: Rename Reiserfs's struct path 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 ` [PATCH 3 of 4] struct path: Move struct path from fs/namei.c into include/linux Josef Jeff Sipek
2006-10-19  0:57 ` [PATCH 4 of 4] struct path: make eCryptfs a user of struct path 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=patchbomb.1161219427@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).