From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>, Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs: take XFS_IOLOCK_EXCL if suid removal is required
Date: Mon, 09 Mar 2015 10:28:53 -0400 [thread overview]
Message-ID: <54FDAE25.6080907@sandeen.net> (raw)
In-Reply-To: <20150306210927.GA13958@dastard>
On 3/6/15 4:09 PM, Dave Chinner wrote:
...
>> Upgrade the lock to XFS_IOLOCK_EXCL in this case.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>
> I believe Jan Kara has already addressed this problem in
> this patchset:
>
> http://oss.sgi.com/archives/xfs/2015-03/msg00051.html
Ah, yes, that should fix it. Thanks Jan.
Sorry for missing it.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-03-09 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 16:54 [PATCH] xfs: take XFS_IOLOCK_EXCL if suid removal is required Eric Sandeen
2015-03-06 21:09 ` Dave Chinner
2015-03-09 14:28 ` Eric Sandeen [this message]
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=54FDAE25.6080907@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox