From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfs: push down inactive transaction mgmt for remote symlinks
Date: Fri, 20 Sep 2013 09:05:26 -0400 [thread overview]
Message-ID: <523C4816.1040105@redhat.com> (raw)
In-Reply-To: <20130918221729.GB9901@dastard>
On 09/18/2013 06:17 PM, Dave Chinner wrote:
> On Wed, Sep 18, 2013 at 12:15:58PM -0400, Brian Foster wrote:
>> Push down the transaction management for remote symlinks from
>> xfs_inactive() down to xfs_inactive_symlink_rmt(). The latter is
>> cleaned up to avoid transaction management intended for the
>> calling context (i.e., trans duplication, reservation, item
>> attachment).
>>
>> Signed-off-by: Brian Foster <bfoster@redhat.com>
>> ---
...
>> diff --git a/fs/xfs/xfs_symlink.c b/fs/xfs/xfs_symlink.c
>> index f622a97..f85f6f2 100644
>> --- a/fs/xfs/xfs_symlink.c
>> +++ b/fs/xfs/xfs_symlink.c
>> @@ -424,8 +424,7 @@ xfs_symlink(
>> */
>> STATIC int
>> xfs_inactive_symlink_rmt(
...
>> /*
>> * The transaction must have been committed, since there were
>> * actually extents freed by xfs_bunmapi. See xfs_bmap_finish.
>> @@ -508,29 +513,16 @@ xfs_inactive_symlink_rmt(
>> * Mark it dirty so it will be logged and moved forward in the log as
>> * part of every commit.
>> */
>> - xfs_trans_ijoin(tp, ip, 0);
>> + xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL);
>
> Oh, good, you caught the "need to unlock the inode at commit" case
> :)
>
Yeah, and while fixing the error handling order issues in v2 I just
noticed that this leaves the final xfs_idata_realloc() call in
xfs_inactive_symlink_rmt() unprotected wrt to the ilock. ;) I'll fix
that up to just do the (un)locking manually here as well for v3...
Brian
>>
>> - error1:
>> +error2:
>> xfs_bmap_cancel(&free_list);
>> - error0:
>> +error1:
>> + xfs_iunlock(ip, XFS_ILOCK_EXCL);
>> +error0:
>> + xfs_trans_cancel(tp, XFS_TRANS_RELEASE_LOG_RES | XFS_TRANS_ABORT);
>> return error;
>
> And the error labels need reworking appropriately.
>
>> }
>>
>> @@ -563,16 +546,13 @@ xfs_inactive_symlink_rmt(
>> */
>> int
>> xfs_inactive_symlink(
>> - struct xfs_inode *ip,
>> - struct xfs_trans **tp)
>> + struct xfs_inode *ip)
>> {
>> struct xfs_mount *mp = ip->i_mount;
>> int pathlen;
>>
>> trace_xfs_inactive_symlink(ip);
>>
>> - ASSERT(xfs_isilocked(ip, XFS_ILOCK_EXCL));
>> -
>> if (XFS_FORCED_SHUTDOWN(mp))
>> return XFS_ERROR(EIO);
>
> The call to xfs_idata_realloc() needs to be done under the
> XFS_ILOCK_EXCL here. We can race with other inode cache lookups
> that do work, so we do need to ensure that we correctly lock
> everything for modifications that are to be made to the inode state.
>
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-20 13:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 16:15 [PATCH 0/3] xfs: rework xfs_inactive() Brian Foster
2013-09-18 16:15 ` [PATCH 1/3] xfs: push down inactive transaction mgmt for remote symlinks Brian Foster
2013-09-18 18:06 ` Brian Foster
2013-09-18 22:51 ` Dave Chinner
2013-09-19 12:43 ` Brian Foster
2013-09-19 23:23 ` Dave Chinner
2013-09-18 22:17 ` Dave Chinner
2013-09-19 12:55 ` Brian Foster
2013-09-20 13:05 ` Brian Foster [this message]
2013-09-18 16:15 ` [PATCH 2/3] xfs: push down inactive transaction mgmt for truncate Brian Foster
2013-09-18 23:00 ` Dave Chinner
2013-09-18 16:16 ` [PATCH 3/3] xfs: push down inactive transaction mgmt for ifree Brian Foster
2013-09-18 23:06 ` Dave Chinner
2013-09-19 12:44 ` Brian Foster
2013-09-19 23:29 ` 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=523C4816.1040105@redhat.com \
--to=bfoster@redhat.com \
--cc=david@fromorbit.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