From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v3 0/4] xfs: tmpfile fixes
Date: Tue, 15 Apr 2014 12:18:22 -0400 [thread overview]
Message-ID: <1397578706-5385-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
Here's a v3 series for the patches previously posted here:
http://oss.sgi.com/archives/xfs/2014-04/msg00181.html
Patches 1 and 2 are just a split-up of the v1 patch:
http://oss.sgi.com/archives/xfs/2014-04/msg00149.html
Note the v1 patch has a reviewed-by, so feel free to drop 1 and 2 here
in favor of that version. Patches 3 and 4 are a couple cleanups in the
xfs_create() path.
Setting the default ACL is dropped until it is determined how that
should be handled for tmpfile(). This means the xfs_iops.c refactor bits
have been dropped as well.
Brian
v3:
- Split up the deadlock fix and inode security initialization into
separate patches. [hch]
- Dropped the default ACL and associated refactor bits for now. [hch]
- Split the xfs_create() tres and xfs_create_tmpfile() cleanups into
separate patches. [hch]
v2:
- Added a generic create helper to inherit the security/acl init. code
in the tmpfile path.
- Added patch 2 to fold xfs_create_tmpfile() into xfs_create().
Brian Foster (4):
xfs: fix tmpfile/selinux ilock deadlock
xfs: initialize inode security on tmpfile creation
xfs: replace on-stack xfs_trans_res with pointer in xfs_create()
xfs: fold xfs_create_tmpfile() into xfs_create()
fs/xfs/xfs_inode.c | 193 +++++++++++++----------------------------------------
fs/xfs/xfs_inode.h | 2 -
fs/xfs/xfs_iops.c | 20 +++++-
fs/xfs/xfs_trace.h | 7 +-
4 files changed, 69 insertions(+), 153 deletions(-)
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-04-15 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 16:18 Brian Foster [this message]
2014-04-15 16:18 ` [PATCH v3 1/4] xfs: fix tmpfile/selinux ilock deadlock Brian Foster
2014-04-15 17:47 ` Christoph Hellwig
2014-04-15 16:18 ` [PATCH v3 2/4] xfs: initialize inode security on tmpfile creation Brian Foster
2014-04-15 17:50 ` Christoph Hellwig
2014-04-15 17:50 ` Christoph Hellwig
2014-04-15 20:04 ` Stephen Smalley
2014-04-15 20:16 ` Stephen Smalley
2014-04-15 20:22 ` Christoph Hellwig
2014-04-15 20:22 ` Christoph Hellwig
2014-04-15 20:21 ` Stephen Smalley
2014-04-16 12:51 ` Stephen Smalley
2014-04-16 14:14 ` Christoph Hellwig
2014-04-16 14:14 ` Christoph Hellwig
2014-04-16 14:14 ` Stephen Smalley
2014-04-16 14:14 ` Stephen Smalley
2014-04-15 16:18 ` [PATCH v3 3/4] xfs: replace on-stack xfs_trans_res with pointer in xfs_create() Brian Foster
2014-04-15 17:50 ` Christoph Hellwig
2014-04-15 16:18 ` [PATCH v3 4/4] xfs: fold xfs_create_tmpfile() into xfs_create() Brian Foster
2014-04-15 17:51 ` Christoph Hellwig
2014-04-15 21:59 ` [PATCH v3 0/4] xfs: tmpfile fixes 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=1397578706-5385-1-git-send-email-bfoster@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.