From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id CF4047F3F for ; Mon, 15 Jun 2015 10:26:43 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay3.corp.sgi.com (Postfix) with ESMTP id 5BEC1AC001 for ; Mon, 15 Jun 2015 08:26:39 -0700 (PDT) Received: from sandeen.net (sandeen.net [63.231.237.45]) by cuda.sgi.com with ESMTP id SQ0IbJ4Lzgy5pCDm for ; Mon, 15 Jun 2015 08:26:38 -0700 (PDT) Message-ID: <557EEEAD.8000701@sandeen.net> Date: Mon, 15 Jun 2015 10:26:37 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: [PATCH] xfs: take XFS_IOLOCK_EXCL if suid removal is required References: <54F9DBAE.2070002@redhat.com> <20150306210927.GA13958@dastard> In-Reply-To: <20150306210927.GA13958@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Dave Chinner , Eric Sandeen Cc: Jan Kara , xfs-oss On 3/6/15 3:09 PM, Dave Chinner wrote: > On Fri, Mar 06, 2015 at 10:54:06AM -0600, Eric Sandeen wrote: >> 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 > > I believe Jan Kara has already addressed this problem in > this patchset: > > http://oss.sgi.com/archives/xfs/2015-03/msg00051.html Seems like that patchset never made it anywhere, though, so this is still an outstanding problem. :( -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs