From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfs: take XFS_IOLOCK_EXCL if suid removal is required
Date: Fri, 06 Mar 2015 10:54:06 -0600 [thread overview]
Message-ID: <54F9DBAE.2070002@redhat.com> (raw)
This sequence:
# rm -f sparsefile
# truncate --size=1m sparsefile
# chmod ugo+rws sparsefile
# ls -l sparsefile
-rwSrwSrw-. 1 root root 1048576 Mar 6 10:29 sparsefile
# su tester
$ xfs_io -d -c "pwrite 0 4096" sparsefile
wrote 4096/4096 bytes at offset 0
4 KiB, 1 ops; 0.0000 sec (21.505 KiB/sec and 5.3763 ops/sec)
$ exit
will lead to a WARN_ON() in notify change, because i_mutex is
not held, and we get to notify_change via suid removal with
only XFS_IOLOCK_SHARED held, i.e. no i_mutex.
Upgrade the lock to XFS_IOLOCK_EXCL in this case.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index a2e1cb8..e64d5b1 100644
--- a/fs/xfs/xfs_file.c
+++ b/fs/xfs/xfs_file.c
@@ -541,7 +541,7 @@ xfs_zero_eof(
*
* Called with the iolocked held either shared and exclusive according to
* @iolock, and returns with it held. Might upgrade the iolock to exclusive
- * if called for a direct write beyond i_size.
+ * if called for a direct write beyond i_size or if suid removal is required.
*/
STATIC ssize_t
xfs_file_aio_write_checks(
@@ -551,6 +551,7 @@ xfs_file_aio_write_checks(
int *iolock)
{
struct inode *inode = file->f_mapping->host;
+ struct dentry *dentry = file->f_path.dentry;
struct xfs_inode *ip = XFS_I(inode);
int error = 0;
@@ -569,9 +570,12 @@ restart:
* write. If zeroing is needed and we are currently holding the
* iolock shared, we need to update it to exclusive which implies
* having to redo all checks before.
+ *
+ * We also must be locked exclusively if this write will require
+ * suid removal; notify_change expects i_mutex to be locked.
*/
- if (*pos > i_size_read(inode)) {
- bool zero = false;
+ if (*pos > i_size_read(inode) || should_remove_suid(dentry)) {
+ bool z = false;
if (*iolock == XFS_IOLOCK_SHARED) {
xfs_rw_iunlock(ip, *iolock);
@@ -579,9 +583,12 @@ restart:
xfs_rw_ilock(ip, *iolock);
goto restart;
}
- error = xfs_zero_eof(ip, *pos, i_size_read(inode), &zero);
- if (error)
- return error;
+
+ if (*pos > i_size_read(inode) ) {
+ error = xfs_zero_eof(ip, *pos, i_size_read(inode), &z);
+ if (error)
+ return error;
+ }
}
/*
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-03-06 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 16:54 Eric Sandeen [this message]
2015-03-06 21:09 ` [PATCH] xfs: take XFS_IOLOCK_EXCL if suid removal is required Dave Chinner
2015-03-09 14:28 ` Eric Sandeen
2015-06-15 15:26 ` Eric Sandeen
2015-07-09 10:17 ` Jan Kara
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=54F9DBAE.2070002@redhat.com \
--to=sandeen@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.