From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: initialize default acls for ->tmpfile()
Date: Mon, 5 May 2014 20:24:03 +1000 [thread overview]
Message-ID: <20140505102403.GV26353@dastard> (raw)
In-Reply-To: <1398951487-15462-1-git-send-email-bfoster@redhat.com>
On Thu, May 01, 2014 at 09:38:07AM -0400, Brian Foster wrote:
> The current tmpfile handler does not initialize default ACLs. Doing so
> within xfs_vn_tmpfile() makes it roughly equivalent to xfs_vn_mknod(),
> which is already used as a common create handler.
>
> xfs_vn_mknod() does not currently have a mechanism to determine whether
> to link the file into the namespace. Therefore, further abstract
> xfs_vn_mknod() into a new xfs_generic_create() handler with a tmpfile
> parameter. This new handler passes a NULL xname to the create and calls
> d_tmpfile() on the dentry when called via ->tmpfile().
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> Hi all,
>
> It appears that we want to initialize default ACLs for ->tmpfile() after
> all. This patch reintroduces the refactoring to initialize security and
> ACLs through the current xfs_vn_mknod(). This is based on top of the
> previously posted series:
>
> http://oss.sgi.com/archives/xfs/2014-04/msg00396.html
>
> Brian
.....
> @@ -1053,25 +1074,7 @@ xfs_vn_tmpfile(
> struct dentry *dentry,
> umode_t mode)
> {
> - int error;
> - struct xfs_inode *ip;
> - struct inode *inode;
> -
> - error = xfs_create(XFS_I(dir), NULL, mode, 0, &ip);
> - if (unlikely(error))
> - return -error;
> -
> - inode = VFS_I(ip);
> -
> - error = xfs_init_security(inode, dir, &dentry->d_name);
> - if (unlikely(error)) {
> - iput(inode);
> - return -error;
> - }
> -
> - d_tmpfile(dentry, inode);
> -
> - return 0;
> + return xfs_generic_create(dir, dentry, mode, 0, true);
> }
This hunk doesn't apply to a 3.15-rc2 kernel - it calls
xfs_create_tmpfile(). Just applying it as is after fixing the hunk
causes a crash in xfs-create(), because the code in the patch is
calling xfs-create ratehr than xfs_create_tmpfile().
Brian, can you regenerate this patch against a current linus tree
(3.15-rc4)?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-05 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 13:38 [PATCH] xfs: initialize default acls for ->tmpfile() Brian Foster
2014-05-02 10:01 ` Christoph Hellwig
2014-05-05 10:24 ` Dave Chinner [this message]
2014-05-05 13:17 ` Brian Foster
2014-05-05 21:05 ` Dave Chinner
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=20140505102403.GV26353@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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;
as well as URLs for NNTP newsgroup(s).