mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, hch@infradead.org, viro@ftp.linux.org.uk,
	mhalcrow@us.ibm.com, penberg@cs.helsinki.fi,
	linux-fsdevel@vger.kernel.org
Subject: fsstack: struct path
Date: Wed, 18 Oct 2006 00:23:23 -0400	[thread overview]
Message-ID: <20061018042323.GA8537@filer.fsl.cs.sunysb.edu> (raw)

Few weeks ago, I noticed that fs/namei.c defines struct path:

struct path {
	struct vfsmount *mnt;
	struct dentry *dentry;
};

I think it would make sense to move it into include/linux/ as it is quite
useful (and it would discourage the (ab)use of struct nameidata.)

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

One, rather unfortunate, fact is that struct path is also defined in
include/linux/reiserfs_fs.h as something completely different - reiserfs
specific.

Any thoughts?

Josef "Jeff" Sipek.

-- 
I already backed up the box once, I can do it again.

             reply	other threads:[~2006-10-18  4:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  4:23 Josef Sipek [this message]
2006-10-18  8:31 ` Andrew Morton
2006-10-18  8:35   ` Al Viro
2006-10-18 14:38     ` Chris Mason
2006-10-18  8:35   ` Andrew Morton
2006-10-18  9:06     ` Al Viro
2006-10-18  9:12       ` Andrew Morton
2006-10-18  9:22         ` Al Viro
2006-10-18  9:27           ` Paul Jackson
2006-10-18  9:34             ` Al Viro
2006-10-18 10:56               ` Jörn Engel
2006-10-18 14:39                 ` Erez Zadok

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=20061018042323.GA8537@filer.fsl.cs.sunysb.edu \
    --to=jsipek@fsl.cs.sunysb.edu \
    --cc=akpm@osdl.org \
    --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=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

all inboxes | Powered by JetHome®