From: Eric Sandeen <sandeen-+82itfer+wXR7s880joybQ@public.gmane.org>
To: Felix Blyakher <felixb-sJ/iWh9BUns@public.gmane.org>
Cc: Alexander Beregalov
<a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Thu, 07 May 2009 20:09:37 -0500 [thread overview]
Message-ID: <4A038651.5010202@sandeen.net> (raw)
In-Reply-To: <ABCCDF18-5100-4891-AF1C-BA9513C8A334-sJ/iWh9BUns@public.gmane.org>
Felix Blyakher wrote:
> I've been chasing this as well, and I found the double xfs iolock
> unlock which is causing xfs_fsr deadlock itself. I have a fix tested.
> The patch is coming.
>
> Felix
>
Oh :) I just sent this one to the list ... :)
XFS: Fix double unlock of inodes in xfs_swap_extents()
commit ef8f7fc549bf345d92f396f5aa7b152b4969cbf7 had an error
where we would try to re-unlock the inodes after they had been
committed in the transaction; this double unlock caused a
=====================================
[ BUG: bad unlock balance detected! ]
-------------------------------------
xfs_fsr/1459 is trying to release lock (&(&ip->i_iolock)->mr_lock) at:
[<e248dedb>] xfs_iunlock+0x2c/0x92 [xfs]
but there are no more locks to release!
Signed-off-by: Eric Sandeen <sandeen-+82itfer+wXR7s880joybQ@public.gmane.org>
---
Index: linux-2.6/fs/xfs/xfs_dfrag.c
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_dfrag.c
+++ linux-2.6/fs/xfs/xfs_dfrag.c
@@ -347,13 +347,15 @@ xfs_swap_extents(
error = xfs_trans_commit(tp, XFS_TRANS_SWAPEXT);
-out_unlock:
- xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
- xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
out:
kmem_free(tempifp);
return error;
+out_unlock:
+ xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ goto out;
+
out_trans_cancel:
xfs_trans_cancel(tp, 0);
goto out_unlock;
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Felix Blyakher <felixb@sgi.com>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Beregalov <a.beregalov@gmail.com>,
xfs@oss.sgi.com
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Thu, 07 May 2009 20:09:37 -0500 [thread overview]
Message-ID: <4A038651.5010202@sandeen.net> (raw)
In-Reply-To: <ABCCDF18-5100-4891-AF1C-BA9513C8A334@sgi.com>
Felix Blyakher wrote:
> I've been chasing this as well, and I found the double xfs iolock
> unlock which is causing xfs_fsr deadlock itself. I have a fix tested.
> The patch is coming.
>
> Felix
>
Oh :) I just sent this one to the list ... :)
XFS: Fix double unlock of inodes in xfs_swap_extents()
commit ef8f7fc549bf345d92f396f5aa7b152b4969cbf7 had an error
where we would try to re-unlock the inodes after they had been
committed in the transaction; this double unlock caused a
=====================================
[ BUG: bad unlock balance detected! ]
-------------------------------------
xfs_fsr/1459 is trying to release lock (&(&ip->i_iolock)->mr_lock) at:
[<e248dedb>] xfs_iunlock+0x2c/0x92 [xfs]
but there are no more locks to release!
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
Index: linux-2.6/fs/xfs/xfs_dfrag.c
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_dfrag.c
+++ linux-2.6/fs/xfs/xfs_dfrag.c
@@ -347,13 +347,15 @@ xfs_swap_extents(
error = xfs_trans_commit(tp, XFS_TRANS_SWAPEXT);
-out_unlock:
- xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
- xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
out:
kmem_free(tempifp);
return error;
+out_unlock:
+ xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ goto out;
+
out_trans_cancel:
xfs_trans_cancel(tp, 0);
goto out_unlock;
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Felix Blyakher <felixb@sgi.com>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Thu, 07 May 2009 20:09:37 -0500 [thread overview]
Message-ID: <4A038651.5010202@sandeen.net> (raw)
In-Reply-To: <ABCCDF18-5100-4891-AF1C-BA9513C8A334@sgi.com>
Felix Blyakher wrote:
> I've been chasing this as well, and I found the double xfs iolock
> unlock which is causing xfs_fsr deadlock itself. I have a fix tested.
> The patch is coming.
>
> Felix
>
Oh :) I just sent this one to the list ... :)
XFS: Fix double unlock of inodes in xfs_swap_extents()
commit ef8f7fc549bf345d92f396f5aa7b152b4969cbf7 had an error
where we would try to re-unlock the inodes after they had been
committed in the transaction; this double unlock caused a
=====================================
[ BUG: bad unlock balance detected! ]
-------------------------------------
xfs_fsr/1459 is trying to release lock (&(&ip->i_iolock)->mr_lock) at:
[<e248dedb>] xfs_iunlock+0x2c/0x92 [xfs]
but there are no more locks to release!
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
Index: linux-2.6/fs/xfs/xfs_dfrag.c
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_dfrag.c
+++ linux-2.6/fs/xfs/xfs_dfrag.c
@@ -347,13 +347,15 @@ xfs_swap_extents(
error = xfs_trans_commit(tp, XFS_TRANS_SWAPEXT);
-out_unlock:
- xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
- xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
out:
kmem_free(tempifp);
return error;
+out_unlock:
+ xfs_iunlock(ip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ xfs_iunlock(tip, XFS_ILOCK_EXCL | XFS_IOLOCK_EXCL);
+ goto out;
+
out_trans_cancel:
xfs_trans_cancel(tp, 0);
goto out_unlock;
next prev parent reply other threads:[~2009-05-08 1:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:33 2.6.30-rc4: xfs_fsr hangs Alexander Beregalov
2009-05-01 20:33 ` Alexander Beregalov
2009-05-01 20:33 ` Alexander Beregalov
[not found] ` <a4423d670905011333s664115bdh1d72392897567c1d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 10:14 ` Heinz Diehl
2009-05-02 10:14 ` Heinz Diehl
2009-05-02 10:14 ` Heinz Diehl
[not found] ` <20090502101405.GA6145-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:35 ` Alexander Beregalov
2009-05-02 18:56 ` Eric Sandeen
2009-05-02 18:56 ` Eric Sandeen
[not found] ` <49FC9762.6010109-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-02 18:59 ` Alexander Beregalov
2009-05-02 18:59 ` Alexander Beregalov
2009-05-02 18:59 ` Alexander Beregalov
[not found] ` <a4423d670905021159k51e91b12h96189005980b5e73-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 20:14 ` Eric Sandeen
2009-05-02 20:14 ` Eric Sandeen
2009-05-02 20:14 ` Eric Sandeen
2009-05-03 1:47 ` Ed Tomlinson
2009-05-03 1:47 ` Ed Tomlinson
2009-05-03 4:58 ` Eric Sandeen
2009-05-03 7:15 ` Alexander Beregalov
2009-05-03 14:30 ` Eric Sandeen
2009-05-03 20:33 ` Alexander Beregalov
2009-05-05 8:54 ` Alexander Beregalov
2009-05-07 23:33 ` Eric Sandeen
2009-05-07 23:33 ` Eric Sandeen
2009-05-07 23:33 ` Eric Sandeen
[not found] ` <4A036FBC.9020201-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-07 23:55 ` Eric Sandeen
2009-05-07 23:55 ` Eric Sandeen
2009-05-07 23:55 ` Eric Sandeen
[not found] ` <4A037503.1070904-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08 1:04 ` Felix Blyakher
2009-05-08 1:04 ` Felix Blyakher
2009-05-08 1:04 ` Felix Blyakher
[not found] ` <ABCCDF18-5100-4891-AF1C-BA9513C8A334-sJ/iWh9BUns@public.gmane.org>
2009-05-08 1:09 ` Eric Sandeen [this message]
2009-05-08 1:09 ` Eric Sandeen
2009-05-08 1:09 ` Eric Sandeen
[not found] ` <4A038651.5010202-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08 1:17 ` Felix Blyakher
2009-05-08 1:17 ` Felix Blyakher
2009-05-08 1:17 ` Felix Blyakher
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=4A038651.5010202@sandeen.net \
--to=sandeen-+82itfer+wxr7s880joybq@public.gmane.org \
--cc=a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=felixb-sJ/iWh9BUns@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org \
/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.