diff for duplicates of <20090415230736.GA22710@elte.hu> diff --git a/a/1.txt b/N1/1.txt index 7c303b3..27bfa29 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -5,37 +5,31 @@ > > > > * Alexander Beregalov <a.beregalov@gmail.com> wrote: > > -> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrot= -e: +> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrote: > >> > Ingo, > >> > > >> > This small patchset fixes some deadlocks I've faced after trying > >> > some pressures with dbench on a reiserfs partition. > >> > -> >> > There is still some work pending such as adding some checks to e= -nsure we +> >> > There is still some work pending such as adding some checks to ensure we > >> > _always_ release the lock before sleeping, as you suggested. -> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bo= -gani. +> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bogani. > >> > And also some optimizations.... > >> > > >> > Thanks, > >> > Frederic. > >> > > >> > Frederic Weisbecker (3): -> >> > =A0 kill-the-BKL/reiserfs: provide a tool to lock only once the = -write lock -> >> > =A0 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_f= -ile -> >> > =A0 kill-the-BKL/reiserfs: only acquire the write lock once in -> >> > =A0 =A0 reiserfs_dirty_inode +> >> > kill-the-BKL/reiserfs: provide a tool to lock only once the write lock +> >> > kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file +> >> > kill-the-BKL/reiserfs: only acquire the write lock once in +> >> > reiserfs_dirty_inode > >> > -> >> > =A0fs/reiserfs/inode.c =A0 =A0 =A0 =A0 | =A0 10 +++++++--- -> >> > =A0fs/reiserfs/lock.c =A0 =A0 =A0 =A0 =A0| =A0 26 ++++++++++++++= -++++++++++++ -> >> > =A0fs/reiserfs/super.c =A0 =A0 =A0 =A0 | =A0 15 +++++++++------ -> >> > =A0include/linux/reiserfs_fs.h | =A0 =A02 ++ -> >> > =A04 files changed, 44 insertions(+), 9 deletions(-) +> >> > fs/reiserfs/inode.c | 10 +++++++--- +> >> > fs/reiserfs/lock.c | 26 ++++++++++++++++++++++++++ +> >> > fs/reiserfs/super.c | 15 +++++++++------ +> >> > include/linux/reiserfs_fs.h | 2 ++ +> >> > 4 files changed, 44 insertions(+), 9 deletions(-) > >> > > >> > >> Hi @@ -53,31 +47,29 @@ ile > > The most coherent way to test this would be to pick up the latest > > core/kill-the-BKL git tree from: > > -> > =A0 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip= -=2Egit core/kill-the-BKL +> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git core/kill-the-BKL > > ->=20 -> I did not know about this branch, now I am testing it and there is=20 +> +> I did not know about this branch, now I am testing it and there is > no more problem with that testcase (dbench). ->=20 +> > I will continue testing. -thanks for testing it! It seems reiserfs with Frederic's changes=20 +thanks for testing it! It seems reiserfs with Frederic's changes appears to be more stable now on your system. -I saw your NFS circular locking kill-the-BKL problem report on LKML=20 +I saw your NFS circular locking kill-the-BKL problem report on LKML - also attached below. -Hopefully someone on the Cc: list with NFS experience can point out=20 +Hopefully someone on the Cc: list with NFS experience can point out the BKL assumption that is causing this. Ingo ------ Forwarded message from Alexander Beregalov <a.beregalov@gmail.com= -> ----- +----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com> ----- Date: Wed, 15 Apr 2009 22:08:01 +0400 -=46rom: Alexander Beregalov <a.beregalov@gmail.com> +From: Alexander Beregalov <a.beregalov@gmail.com> To: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>, linux-nfs@vger.kernel.org Subject: [core/kill-the-BKL] nfs3: possible circular locking dependency @@ -88,9 +80,7 @@ I have pulled core/kill-the-BKL on top of 2.6.30-rc2. device: '0:18': device_add -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= -=3D=3D=3D=3D=3D=3D=3D +======================================================= [ INFO: possible circular locking dependency detected ] 2.6.30-rc2-00057-g30aa902-dirty #5 ------------------------------------------------------- @@ -98,8 +88,7 @@ mount.nfs/1740 is trying to acquire lock: (kernel_mutex){+.+.+.}, at: [<00000000006f32dc>] lock_kernel+0x28/0x3c but task is already holding lock: - (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x22= -8/0x36c + (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x228/0x36c which lock already depends on the new lock. @@ -167,7 +156,6 @@ device: '0:19': device_add ----- End forwarded message ----- -- -To unsubscribe from this list: send the line "unsubscribe reiserfs-deve= -l" in +To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 7e5dc8b..c675146 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -24,37 +24,31 @@ "> >\n" "> > * Alexander Beregalov <a.beregalov@gmail.com> wrote:\n" "> >\n" - "> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrot=\n" - "e:\n" + "> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrote:\n" "> >> > Ingo,\n" "> >> >\n" "> >> > This small patchset fixes some deadlocks I've faced after trying\n" "> >> > some pressures with dbench on a reiserfs partition.\n" "> >> >\n" - "> >> > There is still some work pending such as adding some checks to e=\n" - "nsure we\n" + "> >> > There is still some work pending such as adding some checks to ensure we\n" "> >> > _always_ release the lock before sleeping, as you suggested.\n" - "> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bo=\n" - "gani.\n" + "> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bogani.\n" "> >> > And also some optimizations....\n" "> >> >\n" "> >> > Thanks,\n" "> >> > Frederic.\n" "> >> >\n" "> >> > Frederic Weisbecker (3):\n" - "> >> > =A0 kill-the-BKL/reiserfs: provide a tool to lock only once the =\n" - "write lock\n" - "> >> > =A0 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_f=\n" - "ile\n" - "> >> > =A0 kill-the-BKL/reiserfs: only acquire the write lock once in\n" - "> >> > =A0 =A0 reiserfs_dirty_inode\n" + "> >> > \302\240 kill-the-BKL/reiserfs: provide a tool to lock only once the write lock\n" + "> >> > \302\240 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file\n" + "> >> > \302\240 kill-the-BKL/reiserfs: only acquire the write lock once in\n" + "> >> > \302\240 \302\240 reiserfs_dirty_inode\n" "> >> >\n" - "> >> > =A0fs/reiserfs/inode.c =A0 =A0 =A0 =A0 | =A0 10 +++++++---\n" - "> >> > =A0fs/reiserfs/lock.c =A0 =A0 =A0 =A0 =A0| =A0 26 ++++++++++++++=\n" - "++++++++++++\n" - "> >> > =A0fs/reiserfs/super.c =A0 =A0 =A0 =A0 | =A0 15 +++++++++------\n" - "> >> > =A0include/linux/reiserfs_fs.h | =A0 =A02 ++\n" - "> >> > =A04 files changed, 44 insertions(+), 9 deletions(-)\n" + "> >> > \302\240fs/reiserfs/inode.c \302\240 \302\240 \302\240 \302\240 | \302\240 10 +++++++---\n" + "> >> > \302\240fs/reiserfs/lock.c \302\240 \302\240 \302\240 \302\240 \302\240| \302\240 26 ++++++++++++++++++++++++++\n" + "> >> > \302\240fs/reiserfs/super.c \302\240 \302\240 \302\240 \302\240 | \302\240 15 +++++++++------\n" + "> >> > \302\240include/linux/reiserfs_fs.h | \302\240 \302\2402 ++\n" + "> >> > \302\2404 files changed, 44 insertions(+), 9 deletions(-)\n" "> >> >\n" "> >>\n" "> >> Hi\n" @@ -72,31 +66,29 @@ "> > The most coherent way to test this would be to pick up the latest\n" "> > core/kill-the-BKL git tree from:\n" "> >\n" - "> > =A0 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip=\n" - "=2Egit core/kill-the-BKL\n" + "> > \302\240 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git core/kill-the-BKL\n" "> >\n" - ">=20\n" - "> I did not know about this branch, now I am testing it and there is=20\n" + "> \n" + "> I did not know about this branch, now I am testing it and there is \n" "> no more problem with that testcase (dbench).\n" - ">=20\n" + "> \n" "> I will continue testing.\n" "\n" - "thanks for testing it! It seems reiserfs with Frederic's changes=20\n" + "thanks for testing it! It seems reiserfs with Frederic's changes \n" "appears to be more stable now on your system.\n" "\n" - "I saw your NFS circular locking kill-the-BKL problem report on LKML=20\n" + "I saw your NFS circular locking kill-the-BKL problem report on LKML \n" "- also attached below.\n" "\n" - "Hopefully someone on the Cc: list with NFS experience can point out=20\n" + "Hopefully someone on the Cc: list with NFS experience can point out \n" "the BKL assumption that is causing this.\n" "\n" "\tIngo\n" "\n" - "----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com=\n" - "> -----\n" + "----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com> -----\n" "\n" "Date: Wed, 15 Apr 2009 22:08:01 +0400\n" - "=46rom: Alexander Beregalov <a.beregalov@gmail.com>\n" + "From: Alexander Beregalov <a.beregalov@gmail.com>\n" "To: linux-kernel <linux-kernel@vger.kernel.org>,\n" "\tIngo Molnar <mingo@elte.hu>, linux-nfs@vger.kernel.org\n" "Subject: [core/kill-the-BKL] nfs3: possible circular locking dependency\n" @@ -107,9 +99,7 @@ "\n" "device: '0:18': device_add\n" "\n" - "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\n" - "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\n" - "=3D=3D=3D=3D=3D=3D=3D\n" + "=======================================================\n" "[ INFO: possible circular locking dependency detected ]\n" "2.6.30-rc2-00057-g30aa902-dirty #5\n" "-------------------------------------------------------\n" @@ -117,8 +107,7 @@ " (kernel_mutex){+.+.+.}, at: [<00000000006f32dc>] lock_kernel+0x28/0x3c\n" "\n" "but task is already holding lock:\n" - " (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x22=\n" - "8/0x36c\n" + " (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x228/0x36c\n" "\n" "which lock already depends on the new lock.\n" "\n" @@ -186,9 +175,8 @@ "\n" "----- End forwarded message -----\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe reiserfs-deve=\n" - "l\" in\n" + "To unsubscribe from this list: send the line \"unsubscribe reiserfs-devel\" in\n" "the body of a message to majordomo@vger.kernel.org\n" More majordomo info at http://vger.kernel.org/majordomo-info.html -b827e4b46f576bba2de61bd4c12968e498834e351a0dfefc41f45d6e12f0de13 +4fc04fb97f1f5d8085962a3fce5ee4972f14fc2f3c100e71761754df054442b8
diff --git a/a/1.txt b/N2/1.txt index 7c303b3..d34ac51 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -5,37 +5,31 @@ > > > > * Alexander Beregalov <a.beregalov@gmail.com> wrote: > > -> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrot= -e: +> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrote: > >> > Ingo, > >> > > >> > This small patchset fixes some deadlocks I've faced after trying > >> > some pressures with dbench on a reiserfs partition. > >> > -> >> > There is still some work pending such as adding some checks to e= -nsure we +> >> > There is still some work pending such as adding some checks to ensure we > >> > _always_ release the lock before sleeping, as you suggested. -> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bo= -gani. +> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bogani. > >> > And also some optimizations.... > >> > > >> > Thanks, > >> > Frederic. > >> > > >> > Frederic Weisbecker (3): -> >> > =A0 kill-the-BKL/reiserfs: provide a tool to lock only once the = -write lock -> >> > =A0 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_f= -ile -> >> > =A0 kill-the-BKL/reiserfs: only acquire the write lock once in -> >> > =A0 =A0 reiserfs_dirty_inode +> >> > kill-the-BKL/reiserfs: provide a tool to lock only once the write lock +> >> > kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file +> >> > kill-the-BKL/reiserfs: only acquire the write lock once in +> >> > reiserfs_dirty_inode > >> > -> >> > =A0fs/reiserfs/inode.c =A0 =A0 =A0 =A0 | =A0 10 +++++++--- -> >> > =A0fs/reiserfs/lock.c =A0 =A0 =A0 =A0 =A0| =A0 26 ++++++++++++++= -++++++++++++ -> >> > =A0fs/reiserfs/super.c =A0 =A0 =A0 =A0 | =A0 15 +++++++++------ -> >> > =A0include/linux/reiserfs_fs.h | =A0 =A02 ++ -> >> > =A04 files changed, 44 insertions(+), 9 deletions(-) +> >> > fs/reiserfs/inode.c | 10 +++++++--- +> >> > fs/reiserfs/lock.c | 26 ++++++++++++++++++++++++++ +> >> > fs/reiserfs/super.c | 15 +++++++++------ +> >> > include/linux/reiserfs_fs.h | 2 ++ +> >> > 4 files changed, 44 insertions(+), 9 deletions(-) > >> > > >> > >> Hi @@ -53,31 +47,29 @@ ile > > The most coherent way to test this would be to pick up the latest > > core/kill-the-BKL git tree from: > > -> > =A0 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip= -=2Egit core/kill-the-BKL +> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git core/kill-the-BKL > > ->=20 -> I did not know about this branch, now I am testing it and there is=20 +> +> I did not know about this branch, now I am testing it and there is > no more problem with that testcase (dbench). ->=20 +> > I will continue testing. -thanks for testing it! It seems reiserfs with Frederic's changes=20 +thanks for testing it! It seems reiserfs with Frederic's changes appears to be more stable now on your system. -I saw your NFS circular locking kill-the-BKL problem report on LKML=20 +I saw your NFS circular locking kill-the-BKL problem report on LKML - also attached below. -Hopefully someone on the Cc: list with NFS experience can point out=20 +Hopefully someone on the Cc: list with NFS experience can point out the BKL assumption that is causing this. Ingo ------ Forwarded message from Alexander Beregalov <a.beregalov@gmail.com= -> ----- +----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com> ----- Date: Wed, 15 Apr 2009 22:08:01 +0400 -=46rom: Alexander Beregalov <a.beregalov@gmail.com> +From: Alexander Beregalov <a.beregalov@gmail.com> To: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>, linux-nfs@vger.kernel.org Subject: [core/kill-the-BKL] nfs3: possible circular locking dependency @@ -88,9 +80,7 @@ I have pulled core/kill-the-BKL on top of 2.6.30-rc2. device: '0:18': device_add -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= -=3D=3D=3D=3D=3D=3D=3D +======================================================= [ INFO: possible circular locking dependency detected ] 2.6.30-rc2-00057-g30aa902-dirty #5 ------------------------------------------------------- @@ -98,8 +88,7 @@ mount.nfs/1740 is trying to acquire lock: (kernel_mutex){+.+.+.}, at: [<00000000006f32dc>] lock_kernel+0x28/0x3c but task is already holding lock: - (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x22= -8/0x36c + (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x228/0x36c which lock already depends on the new lock. @@ -166,8 +155,3 @@ Call Trace: device: '0:19': device_add ----- End forwarded message ----- --- -To unsubscribe from this list: send the line "unsubscribe reiserfs-deve= -l" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 7e5dc8b..7cf92d9 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -24,37 +24,31 @@ "> >\n" "> > * Alexander Beregalov <a.beregalov@gmail.com> wrote:\n" "> >\n" - "> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrot=\n" - "e:\n" + "> >> On Tue, Apr 14, 2009 at 05:34:22AM +0200, Frederic Weisbecker wrote:\n" "> >> > Ingo,\n" "> >> >\n" "> >> > This small patchset fixes some deadlocks I've faced after trying\n" "> >> > some pressures with dbench on a reiserfs partition.\n" "> >> >\n" - "> >> > There is still some work pending such as adding some checks to e=\n" - "nsure we\n" + "> >> > There is still some work pending such as adding some checks to ensure we\n" "> >> > _always_ release the lock before sleeping, as you suggested.\n" - "> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bo=\n" - "gani.\n" + "> >> > Also I have to fix a lockdep warning reported by Alessio Igor Bogani.\n" "> >> > And also some optimizations....\n" "> >> >\n" "> >> > Thanks,\n" "> >> > Frederic.\n" "> >> >\n" "> >> > Frederic Weisbecker (3):\n" - "> >> > =A0 kill-the-BKL/reiserfs: provide a tool to lock only once the =\n" - "write lock\n" - "> >> > =A0 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_f=\n" - "ile\n" - "> >> > =A0 kill-the-BKL/reiserfs: only acquire the write lock once in\n" - "> >> > =A0 =A0 reiserfs_dirty_inode\n" + "> >> > \302\240 kill-the-BKL/reiserfs: provide a tool to lock only once the write lock\n" + "> >> > \302\240 kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file\n" + "> >> > \302\240 kill-the-BKL/reiserfs: only acquire the write lock once in\n" + "> >> > \302\240 \302\240 reiserfs_dirty_inode\n" "> >> >\n" - "> >> > =A0fs/reiserfs/inode.c =A0 =A0 =A0 =A0 | =A0 10 +++++++---\n" - "> >> > =A0fs/reiserfs/lock.c =A0 =A0 =A0 =A0 =A0| =A0 26 ++++++++++++++=\n" - "++++++++++++\n" - "> >> > =A0fs/reiserfs/super.c =A0 =A0 =A0 =A0 | =A0 15 +++++++++------\n" - "> >> > =A0include/linux/reiserfs_fs.h | =A0 =A02 ++\n" - "> >> > =A04 files changed, 44 insertions(+), 9 deletions(-)\n" + "> >> > \302\240fs/reiserfs/inode.c \302\240 \302\240 \302\240 \302\240 | \302\240 10 +++++++---\n" + "> >> > \302\240fs/reiserfs/lock.c \302\240 \302\240 \302\240 \302\240 \302\240| \302\240 26 ++++++++++++++++++++++++++\n" + "> >> > \302\240fs/reiserfs/super.c \302\240 \302\240 \302\240 \302\240 | \302\240 15 +++++++++------\n" + "> >> > \302\240include/linux/reiserfs_fs.h | \302\240 \302\2402 ++\n" + "> >> > \302\2404 files changed, 44 insertions(+), 9 deletions(-)\n" "> >> >\n" "> >>\n" "> >> Hi\n" @@ -72,31 +66,29 @@ "> > The most coherent way to test this would be to pick up the latest\n" "> > core/kill-the-BKL git tree from:\n" "> >\n" - "> > =A0 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip=\n" - "=2Egit core/kill-the-BKL\n" + "> > \302\240 git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git core/kill-the-BKL\n" "> >\n" - ">=20\n" - "> I did not know about this branch, now I am testing it and there is=20\n" + "> \n" + "> I did not know about this branch, now I am testing it and there is \n" "> no more problem with that testcase (dbench).\n" - ">=20\n" + "> \n" "> I will continue testing.\n" "\n" - "thanks for testing it! It seems reiserfs with Frederic's changes=20\n" + "thanks for testing it! It seems reiserfs with Frederic's changes \n" "appears to be more stable now on your system.\n" "\n" - "I saw your NFS circular locking kill-the-BKL problem report on LKML=20\n" + "I saw your NFS circular locking kill-the-BKL problem report on LKML \n" "- also attached below.\n" "\n" - "Hopefully someone on the Cc: list with NFS experience can point out=20\n" + "Hopefully someone on the Cc: list with NFS experience can point out \n" "the BKL assumption that is causing this.\n" "\n" "\tIngo\n" "\n" - "----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com=\n" - "> -----\n" + "----- Forwarded message from Alexander Beregalov <a.beregalov@gmail.com> -----\n" "\n" "Date: Wed, 15 Apr 2009 22:08:01 +0400\n" - "=46rom: Alexander Beregalov <a.beregalov@gmail.com>\n" + "From: Alexander Beregalov <a.beregalov@gmail.com>\n" "To: linux-kernel <linux-kernel@vger.kernel.org>,\n" "\tIngo Molnar <mingo@elte.hu>, linux-nfs@vger.kernel.org\n" "Subject: [core/kill-the-BKL] nfs3: possible circular locking dependency\n" @@ -107,9 +99,7 @@ "\n" "device: '0:18': device_add\n" "\n" - "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\n" - "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\n" - "=3D=3D=3D=3D=3D=3D=3D\n" + "=======================================================\n" "[ INFO: possible circular locking dependency detected ]\n" "2.6.30-rc2-00057-g30aa902-dirty #5\n" "-------------------------------------------------------\n" @@ -117,8 +107,7 @@ " (kernel_mutex){+.+.+.}, at: [<00000000006f32dc>] lock_kernel+0x28/0x3c\n" "\n" "but task is already holding lock:\n" - " (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x22=\n" - "8/0x36c\n" + " (&type->s_umount_key#24/1){+.+.+.}, at: [<00000000004b88a0>] sget+0x228/0x36c\n" "\n" "which lock already depends on the new lock.\n" "\n" @@ -184,11 +173,6 @@ " [000000000056401c] nfs_get_root+0x34/0x17c\n" "device: '0:19': device_add\n" "\n" - "----- End forwarded message -----\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe reiserfs-deve=\n" - "l\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + ----- End forwarded message ----- -b827e4b46f576bba2de61bd4c12968e498834e351a0dfefc41f45d6e12f0de13 +af0250b7dac20925e9cdccfe5303a44726956b144457f54484c6e84c9e2efd99
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.