From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] XFS: sanitise VFS inode extraction
Date: Sun, 20 Jul 2008 22:43:45 +1000 [thread overview]
Message-ID: <1216557828-29056-1-git-send-email-david@fromorbit.com> (raw)
Getting the VFS inode from the XFS inode is done in a variety of
ways right now - direct deference or one of two XFS_ITOV macros.
This should be consiѕtent throughout the code - this patch
series does that in a way that is consistent with the opposite
XFS_I() conversion. We now use VFS_I() to extract the VFS inode
from the XFS inode.
Diffstat:
xfs/linux-2.6/xfs_export.c | 6 +++---
xfs/linux-2.6/xfs_fs_subr.c | 6 +++---
xfs/linux-2.6/xfs_ioctl.c | 4 ++--
xfs/linux-2.6/xfs_iops.c | 16 ++++++++--------
xfs/linux-2.6/xfs_iops.h | 6 ------
xfs/linux-2.6/xfs_linux.h | 2 +-
xfs/linux-2.6/xfs_lrw.c | 2 +-
xfs/linux-2.6/xfs_super.c | 6 +++---
xfs/linux-2.6/xfs_vnode.c | 2 +-
xfs/quota/xfs_dquot.c | 2 +-
xfs/quota/xfs_qm_syscalls.c | 2 +-
xfs/xfs_bmap.c | 2 +-
xfs/xfs_dfrag.c | 4 ++--
xfs/xfs_iget.c | 7 ++++---
xfs/xfs_inode.c | 4 ++--
xfs/xfs_inode.h | 24 +++++++++++++++++++-----
xfs/xfs_itable.c | 2 +-
xfs/xfs_utils.c | 4 ++--
xfs/xfs_utils.h | 4 ++--
xfs/xfs_vfsops.c | 10 +++++-----
xfs/xfs_vnodeops.c | 12 ++++++------
21 files changed, 68 insertions(+), 59 deletions(-)
next reply other threads:[~2008-07-20 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 12:43 Dave Chinner [this message]
2008-07-20 12:43 ` [PATCH 1/3] XFS: Avoid directly referencing the VFS inode Dave Chinner
2008-07-20 12:43 ` [PATCH 2/3] XFS: kill shouty XFS_ITOV_NULL macro Dave Chinner
2008-07-20 12:43 ` [PATCH 3/3] XFS: Kill shouty XFS_ITOV() macro Dave Chinner
2008-07-21 8:01 ` [PATCH 0/3] XFS: sanitise VFS inode extraction Christoph Hellwig
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=1216557828-29056-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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