From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: iustin@k1024.org, xfs@oss.sgi.com
Subject: Re: [PATCH 2/9] xfs: separate xflags from xfs_ioctl_setattr
Date: Thu, 29 Jan 2015 10:34:12 -0500 [thread overview]
Message-ID: <20150129153412.GB17652@laptop.bfoster> (raw)
In-Reply-To: <1422328486-24661-3-git-send-email-david@fromorbit.com>
On Tue, Jan 27, 2015 at 02:14:39PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> The setting of the extended flags is down through two separate
> interfaces, but they are munged together into xfs_ioctl_setattr
> and make that function far more complex than it needs to be.
> Separate it out into a helper function along with all the other
> common inode changes and transaction manipulations in
> xfs_ioctl_setattr().
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_ioctl.c | 89 +++++++++++++++++++++++++-----------------------------
> 1 file changed, 41 insertions(+), 48 deletions(-)
>
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index 09325ff..ba98412 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -1013,6 +1013,44 @@ xfs_diflags_to_linux(
> inode->i_flags &= ~S_NOATIME;
> }
>
> +static int
> +xfs_ioctl_setattr_xflags(
> + struct xfs_trans *tp,
> + struct xfs_inode *ip,
> + struct fsxattr *fa)
> +{
> + struct xfs_mount *mp = ip->i_mount;
> +
> + /* Can't change realtime flag if any extents are allocated. */
> + if ((ip->i_d.di_nextents || ip->i_delayed_blks) &&
> + XFS_IS_REALTIME_INODE(ip) != (fa->fsx_xflags & XFS_XFLAG_REALTIME))
> + return -EINVAL;
> +
> + /* If realtime flag is set then must have realtime device */
> + if (fa->fsx_xflags & XFS_XFLAG_REALTIME) {
> + if (mp->m_sb.sb_rblocks == 0 || mp->m_sb.sb_rextsize == 0 ||
> + (ip->i_d.di_extsize % mp->m_sb.sb_rextsize))
> + return -EINVAL;
> + }
> +
> + /*
> + * Can't modify an immutable/append-only file unless
> + * we have appropriate permission.
> + */
> + if (((ip->i_d.di_flags & (XFS_DIFLAG_IMMUTABLE | XFS_DIFLAG_APPEND)) ||
> + (fa->fsx_xflags & (XFS_XFLAG_IMMUTABLE | XFS_XFLAG_APPEND))) &&
> + !capable(CAP_LINUX_IMMUTABLE))
> + return -EPERM;
> +
> + xfs_trans_ijoin(tp, ip, 0);
> + xfs_set_diflags(ip, fa->fsx_xflags);
> + xfs_diflags_to_linux(ip);
> + xfs_trans_ichgtime(tp, ip, XFS_ICHGTIME_CHG);
> + xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> + XFS_STATS_INC(xs_ig_attrchg);
> + return 0;
> +}
> +
> #define FSX_PROJID 1
> #define FSX_EXTSIZE 2
> #define FSX_XFLAGS 4
> @@ -1159,44 +1197,9 @@ xfs_ioctl_setattr(
> }
>
>
> - if (mask & FSX_XFLAGS) {
> - /*
> - * Can't change realtime flag if any extents are allocated.
> - */
> - if ((ip->i_d.di_nextents || ip->i_delayed_blks) &&
> - (XFS_IS_REALTIME_INODE(ip)) !=
> - (fa->fsx_xflags & XFS_XFLAG_REALTIME)) {
> - code = -EINVAL; /* EFBIG? */
> - goto error_return;
> - }
> -
> - /*
> - * If realtime flag is set then must have realtime data.
> - */
> - if ((fa->fsx_xflags & XFS_XFLAG_REALTIME)) {
> - if ((mp->m_sb.sb_rblocks == 0) ||
> - (mp->m_sb.sb_rextsize == 0) ||
> - (ip->i_d.di_extsize % mp->m_sb.sb_rextsize)) {
> - code = -EINVAL;
> - goto error_return;
> - }
> - }
> -
> - /*
> - * Can't modify an immutable/append-only file unless
> - * we have appropriate permission.
> - */
> - if ((ip->i_d.di_flags &
> - (XFS_DIFLAG_IMMUTABLE|XFS_DIFLAG_APPEND) ||
> - (fa->fsx_xflags &
> - (XFS_XFLAG_IMMUTABLE | XFS_XFLAG_APPEND))) &&
> - !capable(CAP_LINUX_IMMUTABLE)) {
> - code = -EPERM;
> - goto error_return;
> - }
> - }
> -
> - xfs_trans_ijoin(tp, ip, 0);
> + code = xfs_ioctl_setattr_xflags(tp, ip, fa);
> + if (code)
> + goto error_return;
>
> /*
> * Change file ownership. Must be the owner or privileged.
> @@ -1227,11 +1230,6 @@ xfs_ioctl_setattr(
>
> }
>
> - if (mask & FSX_XFLAGS) {
> - xfs_set_diflags(ip, fa->fsx_xflags);
> - xfs_diflags_to_linux(ip);
> - }
> -
> /*
> * Only set the extent size hint if we've already determined that the
> * extent size hint should be set on the inode. If no extent size flags
> @@ -1246,11 +1244,6 @@ xfs_ioctl_setattr(
> ip->i_d.di_extsize = extsize;
> }
>
> - xfs_trans_ichgtime(tp, ip, XFS_ICHGTIME_CHG);
> - xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> -
> - XFS_STATS_INC(xs_ig_attrchg);
> -
> /*
> * If this is a synchronous mount, make sure that the
> * transaction goes to disk before returning to the user.
> --
> 2.0.0
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-29 15:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 3:14 [PATCH 0/9] xfs: xfs_ioctl_setxattr rework Dave Chinner
2015-01-27 3:14 ` [PATCH 1/9] xfs: FSX_NONBLOCK is not used Dave Chinner
2015-01-29 15:33 ` Brian Foster
2015-01-27 3:14 ` [PATCH 2/9] xfs: separate xflags from xfs_ioctl_setattr Dave Chinner
2015-01-29 15:34 ` Brian Foster [this message]
2015-01-27 3:14 ` [PATCH 3/9] xfs: factor out xfs_ioctl_setattr transaciton preamble Dave Chinner
2015-01-29 15:34 ` Brian Foster
2015-01-27 3:14 ` [PATCH 4/9] xfs: disaggregate xfs_ioctl_setattr Dave Chinner
2015-01-29 15:34 ` Brian Foster
2015-01-27 3:14 ` [PATCH 5/9] xfs: kill xfs_ioctl_setattr behaviour mask Dave Chinner
2015-01-29 15:35 ` Brian Foster
2015-01-27 3:14 ` [PATCH 6/9] xfs: XFS_IOCTL_SETXATTR can run in user namespaces Dave Chinner
2015-01-29 15:35 ` Brian Foster
2015-01-29 23:53 ` Dave Chinner
2015-01-30 3:04 ` Brian Foster
2015-01-30 7:44 ` Dave Chinner
2015-01-27 3:14 ` [PATCH 7/9] xfs; factor extsize hint checking out of xfs_ioctl_setattr Dave Chinner
2015-01-29 15:35 ` Brian Foster
2015-01-27 3:14 ` [PATCH 8/9] xfs; factor projid " Dave Chinner
2015-01-29 15:35 ` Brian Foster
2015-01-27 3:14 ` [PATCH 9/9] xfs: fix behaviour of XFS_IOC_FSSETXATTR on directories Dave Chinner
2015-01-29 15:35 ` Brian Foster
2015-01-29 15:38 ` [PATCH 0/9] xfs: xfs_ioctl_setxattr rework Brian Foster
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=20150129153412.GB17652@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=iustin@k1024.org \
--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