From: Lachlan McIlroy <lachlan@sgi.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: [PATCH] Unlock inode before calling xfs_idestroy()
Date: Mon, 22 Sep 2008 13:52:22 +1000 [thread overview]
Message-ID: <48D71676.5080808@sgi.com> (raw)
In-Reply-To: <48D326A7.6070508@sgi.com>
Timothy Shimmin wrote:
> Lachlan McIlroy wrote:
>> Lock debugging reported the ilock was being destroyed
>> without being unlocked.
>>
>> --- a/fs/xfs/xfs_iget.c 2008-09-19 13:03:57.000000000 +1000
>> +++ b/fs/xfs/xfs_iget.c 2008-09-19 13:12:38.000000000 +1000
>> @@ -214,6 +214,7 @@ finish_inode:
>> xfs_ilock(ip, lock_flags);
>>
>> if ((ip->i_d.di_mode == 0) && !(flags & XFS_IGET_CREATE)) {
>> + xfs_iunlock(ip, lock_flags);
>> xfs_idestroy(ip);
>> xfs_put_perag(mp, pag);
>> return ENOENT;
>> @@ -224,6 +225,7 @@ finish_inode:
>> * write spinlock.
>> */
>> if (radix_tree_preload(GFP_KERNEL)) {
>> + xfs_iunlock(ip, lock_flags);
>> xfs_idestroy(ip);
>> delay(1);
>> goto again;
>> @@ -239,6 +241,7 @@ finish_inode:
>> BUG_ON(error != -EEXIST);
>> write_unlock(&pag->pag_ici_lock);
>> radix_tree_preload_end();
>> + xfs_iunlock(ip, lock_flags);
>> xfs_idestroy(ip);
>> XFS_STATS_INC(xs_ig_dup);
>> goto again;
>
> I'm just wondering about the case where lock_flags==0
> and the inode is not locked.
> I think it would fail an assert in xfs_iunlock().
Good catch Tim, thanks.
>
>
> --Tim
>
>
> if (lock_flags)
> xfs_ilock(ip, lock_flags);
>
> if ((ip->i_d.di_mode == 0) && !(flags & XFS_IGET_CREATE)) {
> xfs_iunlock(ip, lock_flags);
> xfs_idestroy(ip);
> xfs_put_perag(mp, pag);
> return ENOENT;
> }
>
> void
> xfs_iunlock(
> xfs_inode_t *ip,
> uint lock_flags)
> {
> /*
> * You can't set both SHARED and EXCL for the same lock,
> * and only XFS_IOLOCK_SHARED, XFS_IOLOCK_EXCL, XFS_ILOCK_SHARED,
> * and XFS_ILOCK_EXCL are valid values to set in lock_flags.
> */
> ASSERT((lock_flags & (XFS_IOLOCK_SHARED | XFS_IOLOCK_EXCL)) !=
> (XFS_IOLOCK_SHARED | XFS_IOLOCK_EXCL));
> ASSERT((lock_flags & (XFS_ILOCK_SHARED | XFS_ILOCK_EXCL)) !=
> (XFS_ILOCK_SHARED | XFS_ILOCK_EXCL));
> ASSERT((lock_flags & ~(XFS_LOCK_MASK | XFS_IUNLOCK_NONOTIFY |
> XFS_LOCK_DEP_MASK)) == 0);
> ASSERT(lock_flags != 0);
>
>
next prev parent reply other threads:[~2008-09-22 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 3:15 [PATCH] Unlock inode before calling xfs_idestroy() Lachlan McIlroy
2008-09-19 4:12 ` Timothy Shimmin
2008-09-22 3:52 ` Lachlan McIlroy [this message]
2008-09-19 7:26 ` Christoph Hellwig
2008-09-22 3:57 ` Lachlan McIlroy
2008-09-20 7:01 ` Dave Chinner
2008-09-22 3:59 ` Lachlan McIlroy
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=48D71676.5080808@sgi.com \
--to=lachlan@sgi.com \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.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