Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Thu, 2007-12-13 at 00:42 +0100, Andi Kleen wrote: > > I appear to have misread d_find_alias(). It would seem that the only way > > to ensure that a mountpoint won't be found is to remove it altogether > > from the inode->i_dentry list. AFAICS that should be largely harmless > > since the nfs sb->s_root is never visible to users, and is never part of > > a dentry tree. > > Hasn't BUGed so far with this patch. I'll watch it further but it looks > good so far. Thanks. I would suggest to push the patch. > > -Andi Thanks Andi! I'll push it together with the other patches asap. Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
> I appear to have misread d_find_alias(). It would seem that the only way > to ensure that a mountpoint won't be found is to remove it altogether > from the inode->i_dentry list. AFAICS that should be largely harmless > since the nfs sb->s_root is never visible to users, and is never part of > a dentry tree. Hasn't BUGed so far with this patch. I'll watch it further but it looks good so far. Thanks. I would suggest to push the patch. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
I appear to have misread d_find_alias(). It would seem that the only way to ensure that a mountpoint won't be found is to remove it altogether from the inode-i_dentry list. AFAICS that should be largely harmless since the nfs sb-s_root is never visible to users, and is never part of a dentry tree. Hasn't BUGed so far with this patch. I'll watch it further but it looks good so far. Thanks. I would suggest to push the patch. -Andi -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Thu, 2007-12-13 at 00:42 +0100, Andi Kleen wrote: I appear to have misread d_find_alias(). It would seem that the only way to ensure that a mountpoint won't be found is to remove it altogether from the inode-i_dentry list. AFAICS that should be largely harmless since the nfs sb-s_root is never visible to users, and is never part of a dentry tree. Hasn't BUGed so far with this patch. I'll watch it further but it looks good so far. Thanks. I would suggest to push the patch. -Andi Thanks Andi! I'll push it together with the other patches asap. Cheers Trond -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Mon, 2007-12-10 at 19:57 +0100, Andi Kleen wrote: > > Hi Andi, > > > > Does the attached patch fix the Oops? > > Nope, got that a few hours after boot again: > > -Andi Hi Andi, I appear to have misread d_find_alias(). It would seem that the only way to ensure that a mountpoint won't be found is to remove it altogether from the inode->i_dentry list. AFAICS that should be largely harmless since the nfs sb->s_root is never visible to users, and is never part of a dentry tree. Cheers Trond --- Begin Message --- Ensure that the dummy 'root dentry' is invisible to d_find_alias(). If not, then it may be spliced into the tree if a parent directory from the same filesystem gets mounted at a later time. Signed-off-by: Trond Myklebust <[EMAIL PROTECTED]> --- fs/nfs/getroot.c | 11 +++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/fs/nfs/getroot.c b/fs/nfs/getroot.c index 0ee4384..e6242cd 100644 --- a/fs/nfs/getroot.c +++ b/fs/nfs/getroot.c @@ -57,6 +57,17 @@ static int nfs_superblock_set_dummy_root(struct super_block *sb, struct inode *i } /* Circumvent igrab(): we know the inode is not being freed */ atomic_inc(>i_count); + /* +* Ensure that this dentry is invisible to d_find_alias(). +* Otherwise, it may be spliced into the tree by +* d_materialise_unique if a parent directory from the same +* filesystem gets mounted at a later time. +* This again causes shrink_dcache_for_umount_subtree() to +* Oops, since the test for IS_ROOT() will fail. +*/ + spin_lock(_lock); + list_del_init(>s_root->d_alias); + spin_unlock(_lock); } return 0; } --- End Message ---
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Mon, 2007-12-10 at 19:57 +0100, Andi Kleen wrote: Hi Andi, Does the attached patch fix the Oops? Nope, got that a few hours after boot again: -Andi Hi Andi, I appear to have misread d_find_alias(). It would seem that the only way to ensure that a mountpoint won't be found is to remove it altogether from the inode-i_dentry list. AFAICS that should be largely harmless since the nfs sb-s_root is never visible to users, and is never part of a dentry tree. Cheers Trond ---BeginMessage--- Ensure that the dummy 'root dentry' is invisible to d_find_alias(). If not, then it may be spliced into the tree if a parent directory from the same filesystem gets mounted at a later time. Signed-off-by: Trond Myklebust [EMAIL PROTECTED] --- fs/nfs/getroot.c | 11 +++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/fs/nfs/getroot.c b/fs/nfs/getroot.c index 0ee4384..e6242cd 100644 --- a/fs/nfs/getroot.c +++ b/fs/nfs/getroot.c @@ -57,6 +57,17 @@ static int nfs_superblock_set_dummy_root(struct super_block *sb, struct inode *i } /* Circumvent igrab(): we know the inode is not being freed */ atomic_inc(inode-i_count); + /* +* Ensure that this dentry is invisible to d_find_alias(). +* Otherwise, it may be spliced into the tree by +* d_materialise_unique if a parent directory from the same +* filesystem gets mounted at a later time. +* This again causes shrink_dcache_for_umount_subtree() to +* Oops, since the test for IS_ROOT() will fail. +*/ + spin_lock(dcache_lock); + list_del_init(sb-s_root-d_alias); + spin_unlock(dcache_lock); } return 0; } ---End Message---
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
> Hi Andi, > > Does the attached patch fix the Oops? Nope, got that a few hours after boot again: -Andi EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. [ cut here ] kernel BUG at fs/dcache.c:595! invalid opcode: [1] SMP CPU 0 Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 shpchp container pci_hotplug button iTCO_wdt rtc_cmos i2c_i801 rtc_core rtc_lib i2c_core sr_mod cdrom iTCO_vendor_support sg floppy ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor Pid: 30784, comm: umount.nfs Not tainted 2.6.24-rc4-git3-2-vanilla #1 RIP: 0010:[] [] shrink_dcache_for_umount_subtree+0x16/0x241 RSP: 0018:8101530c5e18 EFLAGS: 00010202 RAX: RBX: 8101b2873080 RCX: RDX: RSI: 0296 RDI: 8101b2873080 RBP: 810153dddcb0 R08: 8101db008d10 R09: 0296 R10: 8101db008d10 R11: 0400 R12: 810225c27000 R13: R14: 55769040 R15: FS: 2b8c13dd16f0() GS:8050d000() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 2ab9197bc315 CR3: 0001db56c000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process umount.nfs (pid: 30784, threadinfo 8101530c4000, task 810224c7d040) Stack: 0296 810225c27000 883e7be0 810225c27000 802a6288 810225c27000 80297afc 8101db008c80 0018 883ffe60 80297bfb Call Trace: [] shrink_dcache_for_umount+0x2f/0x3d [] generic_shutdown_super+0x19/0xf1 [] kill_anon_super+0x9/0x35 [] :nfs:nfs_kill_super+0xd/0x16 [] deactivate_super+0x6a/0x83 [] sys_umount+0x23c/0x24d [] d_kill+0x40/0x55 [] dput+0x26/0x115 [] __fput+0x14a/0x179 [] mntput_no_expire+0x1f/0x86 [] filp_close+0x5a/0x61 [] system_call+0x7e/0x83 Code: 0f 0b eb fe 48 c7 c7 80 16 62 80 e8 d7 bc 16 00 48 8b 53 40 RIP [] shrink_dcache_for_umount_subtree+0x16/0x241 RSP -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
Hi Andi, Does the attached patch fix the Oops? Nope, got that a few hours after boot again: -Andi EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. [ cut here ] kernel BUG at fs/dcache.c:595! invalid opcode: [1] SMP CPU 0 Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 shpchp container pci_hotplug button iTCO_wdt rtc_cmos i2c_i801 rtc_core rtc_lib i2c_core sr_mod cdrom iTCO_vendor_support sg floppy ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor Pid: 30784, comm: umount.nfs Not tainted 2.6.24-rc4-git3-2-vanilla #1 RIP: 0010:[802a602e] [802a602e] shrink_dcache_for_umount_subtree+0x16/0x241 RSP: 0018:8101530c5e18 EFLAGS: 00010202 RAX: RBX: 8101b2873080 RCX: RDX: RSI: 0296 RDI: 8101b2873080 RBP: 810153dddcb0 R08: 8101db008d10 R09: 0296 R10: 8101db008d10 R11: 0400 R12: 810225c27000 R13: R14: 55769040 R15: FS: 2b8c13dd16f0() GS:8050d000() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 2ab9197bc315 CR3: 0001db56c000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process umount.nfs (pid: 30784, threadinfo 8101530c4000, task 810224c7d040) Stack: 0296 810225c27000 883e7be0 810225c27000 802a6288 810225c27000 80297afc 8101db008c80 0018 883ffe60 80297bfb Call Trace: [802a6288] shrink_dcache_for_umount+0x2f/0x3d [80297afc] generic_shutdown_super+0x19/0xf1 [80297bfb] kill_anon_super+0x9/0x35 [883cb1c2] :nfs:nfs_kill_super+0xd/0x16 [80297cac] deactivate_super+0x6a/0x83 [802ab2b4] sys_umount+0x23c/0x24d [802a585a] d_kill+0x40/0x55 [802a6d77] dput+0x26/0x115 [80296d9a] __fput+0x14a/0x179 [802aa70d] mntput_no_expire+0x1f/0x86 [8029442a] filp_close+0x5a/0x61 [8020bfbe] system_call+0x7e/0x83 Code: 0f 0b eb fe 48 c7 c7 80 16 62 80 e8 d7 bc 16 00 48 8b 53 40 RIP [802a602e] shrink_dcache_for_umount_subtree+0x16/0x241 RSP 8101530c5e18 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Sat, 2007-12-08 at 14:22 +0100, Andi Kleen wrote: > [39943.212533] [ cut here ] > [39943.221973] kernel BUG at fs/dcache.c:595! > [39943.230369] invalid opcode: [1] SMP > [39943.238638] last sysfs file: > /devices/system/cpu/cpu7/cache/index2/shared_cpu_map > [39943.253998] CPU 3 > [39943.258283] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 > iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 > cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq > dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 i2c_i801 shpchp container > pci_hotplug button iTCO_wdt rtc_cmos rtc_core i2c_core iTCO_vendor_support > rtc_lib sr_mod cdrom floppy sg ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs > fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor > [39943.351718] Pid: 31869, comm: umount.nfs Tainted: G N > 2.6.24-rc4-git3-20071206230004-default #1 > [39943.370555] RIP: 0010:[] [] > shrink_dcache_for_umount_subtree+0x16/0x241 > [39943.390671] RSP: 0018:8101dc88fe18 EFLAGS: 00010206 > [39943.401552] RAX: RBX: 8100840893c0 RCX: > > [39943.416040] RDX: RSI: 0296 RDI: > 8100840893c0 > [39943.430504] RBP: 8100084fff20 R08: 81004d0a6850 R09: > 0296 > [39943.444969] R10: 81004d0a6850 R11: 802f778c R12: > 810222439400 > [39943.459424] R13: R14: 7fef065cdf00 R15: > > [39943.473887] FS: 7fef052ad6f0() GS:810226419940() > knlGS: > [39943.490452] CS: 0010 DS: ES: CR0: 8005003b > [39943.502134] CR2: 7f5793a36580 CR3: 00021ee38000 CR4: > 06e0 > [39943.516599] DR0: DR1: DR2: > > [39943.531049] DR3: DR6: 0ff0 DR7: > 0400 > [39943.545507] Process umount.nfs (pid: 31869, threadinfo 8101dc88e000, > task 81021ef3b080) > [39943.563289] Stack: 0296 810222439400 883e9be0 > 810222439400 > [39943.579846] 802a6728 810222439400 > 80297e34 > [39943.595152] 81004d0a67c0 0017 88401a80 > 80297f33 > [39943.609871] Call Trace: > [39943.615566] [] shrink_dcache_for_umount+0x2f/0x3d > [39943.628463] [] generic_shutdown_super+0x19/0xf1 > [39943.641011] [] kill_anon_super+0x9/0x35 > [39943.652193] [] :nfs:nfs_kill_super+0xd/0x16 > [39943.664037] [] deactivate_super+0x6a/0x83 > [39943.675537] [] sys_umount+0x23c/0x24d > [39943.686361] [] d_kill+0x40/0x55 > [39943.696139] [] dput+0x26/0x115 > [39943.705745] [] __fput+0x14a/0x179 > [39943.715861] [] mntput_no_expire+0x1f/0x86 > [39943.727375] [] filp_close+0x5a/0x61 > [39943.737853] [] system_call+0x7e/0x83 > [39943.748495] > [39943.751674] > [39943.751675] Code: 0f 0b eb fe 48 c7 c7 80 06 63 80 e8 67 75 17 00 48 8b 53 > 40 > [39943.770405] RIP [] > shrink_dcache_for_umount_subtree+0x16/0x241 > [39943.785790] RSP > [82148.423473] JBD: barrier-based sync failed on dm-1 - disabling barriers Hi Andi, Does the attached patch fix the Oops? Cheers Trond --- Begin Message --- Ensure that the dummy 'root dentry' is invisible to d_find_alias(). If not, then it may be spliced into the tree if a parent directory from the same filesystem gets mounted at a later time. Signed-off-by: Trond Myklebust <[EMAIL PROTECTED]> --- fs/nfs/getroot.c |9 + 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/fs/nfs/getroot.c b/fs/nfs/getroot.c index 0ee4384..076987e 100644 --- a/fs/nfs/getroot.c +++ b/fs/nfs/getroot.c @@ -57,6 +57,15 @@ static int nfs_superblock_set_dummy_root(struct super_block *sb, struct inode *i } /* Circumvent igrab(): we know the inode is not being freed */ atomic_inc(>i_count); + /* +* Ensure that this dentry is invisible to d_find_alias(). +* Otherwise, it may be spliced into the tree by +* d_materialise_unique if a parent directory from the same +* filesystem gets mounted at a later time. +* This again causes shrink_dcache_for_umount_subtree() to +* Oops, since the test for IS_ROOT() will fail. +*/ + sb->s_root->d_flags |= DCACHE_DISCONNECTED; } return 0; } --- End Message ---
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Sat, 2007-12-08 at 14:22 +0100, Andi Kleen wrote: [39943.212533] [ cut here ] [39943.221973] kernel BUG at fs/dcache.c:595! [39943.230369] invalid opcode: [1] SMP [39943.238638] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [39943.253998] CPU 3 [39943.258283] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 i2c_i801 shpchp container pci_hotplug button iTCO_wdt rtc_cmos rtc_core i2c_core iTCO_vendor_support rtc_lib sr_mod cdrom floppy sg ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor [39943.351718] Pid: 31869, comm: umount.nfs Tainted: G N 2.6.24-rc4-git3-20071206230004-default #1 [39943.370555] RIP: 0010:[802a64ce] [802a64ce] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.390671] RSP: 0018:8101dc88fe18 EFLAGS: 00010206 [39943.401552] RAX: RBX: 8100840893c0 RCX: [39943.416040] RDX: RSI: 0296 RDI: 8100840893c0 [39943.430504] RBP: 8100084fff20 R08: 81004d0a6850 R09: 0296 [39943.444969] R10: 81004d0a6850 R11: 802f778c R12: 810222439400 [39943.459424] R13: R14: 7fef065cdf00 R15: [39943.473887] FS: 7fef052ad6f0() GS:810226419940() knlGS: [39943.490452] CS: 0010 DS: ES: CR0: 8005003b [39943.502134] CR2: 7f5793a36580 CR3: 00021ee38000 CR4: 06e0 [39943.516599] DR0: DR1: DR2: [39943.531049] DR3: DR6: 0ff0 DR7: 0400 [39943.545507] Process umount.nfs (pid: 31869, threadinfo 8101dc88e000, task 81021ef3b080) [39943.563289] Stack: 0296 810222439400 883e9be0 810222439400 [39943.579846] 802a6728 810222439400 80297e34 [39943.595152] 81004d0a67c0 0017 88401a80 80297f33 [39943.609871] Call Trace: [39943.615566] [802a6728] shrink_dcache_for_umount+0x2f/0x3d [39943.628463] [80297e34] generic_shutdown_super+0x19/0xf1 [39943.641011] [80297f33] kill_anon_super+0x9/0x35 [39943.652193] [883cd1ba] :nfs:nfs_kill_super+0xd/0x16 [39943.664037] [80297fe4] deactivate_super+0x6a/0x83 [39943.675537] [802ab8ab] sys_umount+0x23c/0x24d [39943.686361] [802a5c8a] d_kill+0x40/0x55 [39943.696139] [802a7217] dput+0x26/0x115 [39943.705745] [802970c0] __fput+0x14a/0x179 [39943.715861] [802aabd1] mntput_no_expire+0x1f/0x86 [39943.727375] [802946ea] filp_close+0x5a/0x61 [39943.737853] [8020bfde] system_call+0x7e/0x83 [39943.748495] [39943.751674] [39943.751675] Code: 0f 0b eb fe 48 c7 c7 80 06 63 80 e8 67 75 17 00 48 8b 53 40 [39943.770405] RIP [802a64ce] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.785790] RSP 8101dc88fe18 [82148.423473] JBD: barrier-based sync failed on dm-1 - disabling barriers Hi Andi, Does the attached patch fix the Oops? Cheers Trond ---BeginMessage--- Ensure that the dummy 'root dentry' is invisible to d_find_alias(). If not, then it may be spliced into the tree if a parent directory from the same filesystem gets mounted at a later time. Signed-off-by: Trond Myklebust [EMAIL PROTECTED] --- fs/nfs/getroot.c |9 + 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/fs/nfs/getroot.c b/fs/nfs/getroot.c index 0ee4384..076987e 100644 --- a/fs/nfs/getroot.c +++ b/fs/nfs/getroot.c @@ -57,6 +57,15 @@ static int nfs_superblock_set_dummy_root(struct super_block *sb, struct inode *i } /* Circumvent igrab(): we know the inode is not being freed */ atomic_inc(inode-i_count); + /* +* Ensure that this dentry is invisible to d_find_alias(). +* Otherwise, it may be spliced into the tree by +* d_materialise_unique if a parent directory from the same +* filesystem gets mounted at a later time. +* This again causes shrink_dcache_for_umount_subtree() to +* Oops, since the test for IS_ROOT() will fail. +*/ + sb-s_root-d_flags |= DCACHE_DISCONNECTED; } return 0; } ---End Message---
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Monday 03 December 2007 16:23:58 Andi Kleen wrote: > > FYI > > Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, > but they're not changing anything near this AFAIK) Got it again after rebooting the system. Can this be made a 2.6.24 blocker or something? Admittedly that was with a few suse patches again; I'll double check it happens in a vanilla kernel too although I don't think there is anything touching this area. The system runs autofs and mounts/umounts NFS servers regularly. -Andi [39943.212533] [ cut here ] [39943.221973] kernel BUG at fs/dcache.c:595! [39943.230369] invalid opcode: [1] SMP [39943.238638] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [39943.253998] CPU 3 [39943.258283] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 i2c_i801 shpchp container pci_hotplug button iTCO_wdt rtc_cmos rtc_core i2c_core iTCO_vendor_support rtc_lib sr_mod cdrom floppy sg ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor [39943.351718] Pid: 31869, comm: umount.nfs Tainted: G N 2.6.24-rc4-git3-20071206230004-default #1 [39943.370555] RIP: 0010:[] [] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.390671] RSP: 0018:8101dc88fe18 EFLAGS: 00010206 [39943.401552] RAX: RBX: 8100840893c0 RCX: [39943.416040] RDX: RSI: 0296 RDI: 8100840893c0 [39943.430504] RBP: 8100084fff20 R08: 81004d0a6850 R09: 0296 [39943.444969] R10: 81004d0a6850 R11: 802f778c R12: 810222439400 [39943.459424] R13: R14: 7fef065cdf00 R15: [39943.473887] FS: 7fef052ad6f0() GS:810226419940() knlGS: [39943.490452] CS: 0010 DS: ES: CR0: 8005003b [39943.502134] CR2: 7f5793a36580 CR3: 00021ee38000 CR4: 06e0 [39943.516599] DR0: DR1: DR2: [39943.531049] DR3: DR6: 0ff0 DR7: 0400 [39943.545507] Process umount.nfs (pid: 31869, threadinfo 8101dc88e000, task 81021ef3b080) [39943.563289] Stack: 0296 810222439400 883e9be0 810222439400 [39943.579846] 802a6728 810222439400 80297e34 [39943.595152] 81004d0a67c0 0017 88401a80 80297f33 [39943.609871] Call Trace: [39943.615566] [] shrink_dcache_for_umount+0x2f/0x3d [39943.628463] [] generic_shutdown_super+0x19/0xf1 [39943.641011] [] kill_anon_super+0x9/0x35 [39943.652193] [] :nfs:nfs_kill_super+0xd/0x16 [39943.664037] [] deactivate_super+0x6a/0x83 [39943.675537] [] sys_umount+0x23c/0x24d [39943.686361] [] d_kill+0x40/0x55 [39943.696139] [] dput+0x26/0x115 [39943.705745] [] __fput+0x14a/0x179 [39943.715861] [] mntput_no_expire+0x1f/0x86 [39943.727375] [] filp_close+0x5a/0x61 [39943.737853] [] system_call+0x7e/0x83 [39943.748495] [39943.751674] [39943.751675] Code: 0f 0b eb fe 48 c7 c7 80 06 63 80 e8 67 75 17 00 48 8b 53 40 [39943.770405] RIP [] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.785790] RSP [82148.423473] JBD: barrier-based sync failed on dm-1 - disabling barriers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Monday 03 December 2007 16:23:58 Andi Kleen wrote: FYI Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, but they're not changing anything near this AFAIK) Got it again after rebooting the system. Can this be made a 2.6.24 blocker or something? Admittedly that was with a few suse patches again; I'll double check it happens in a vanilla kernel too although I don't think there is anything touching this area. The system runs autofs and mounts/umounts NFS servers regularly. -Andi [39943.212533] [ cut here ] [39943.221973] kernel BUG at fs/dcache.c:595! [39943.230369] invalid opcode: [1] SMP [39943.238638] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [39943.253998] CPU 3 [39943.258283] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod e1000 i2c_i801 shpchp container pci_hotplug button iTCO_wdt rtc_cmos rtc_core i2c_core iTCO_vendor_support rtc_lib sr_mod cdrom floppy sg ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_piix ahci libata scsi_mod thermal processor [39943.351718] Pid: 31869, comm: umount.nfs Tainted: G N 2.6.24-rc4-git3-20071206230004-default #1 [39943.370555] RIP: 0010:[802a64ce] [802a64ce] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.390671] RSP: 0018:8101dc88fe18 EFLAGS: 00010206 [39943.401552] RAX: RBX: 8100840893c0 RCX: [39943.416040] RDX: RSI: 0296 RDI: 8100840893c0 [39943.430504] RBP: 8100084fff20 R08: 81004d0a6850 R09: 0296 [39943.444969] R10: 81004d0a6850 R11: 802f778c R12: 810222439400 [39943.459424] R13: R14: 7fef065cdf00 R15: [39943.473887] FS: 7fef052ad6f0() GS:810226419940() knlGS: [39943.490452] CS: 0010 DS: ES: CR0: 8005003b [39943.502134] CR2: 7f5793a36580 CR3: 00021ee38000 CR4: 06e0 [39943.516599] DR0: DR1: DR2: [39943.531049] DR3: DR6: 0ff0 DR7: 0400 [39943.545507] Process umount.nfs (pid: 31869, threadinfo 8101dc88e000, task 81021ef3b080) [39943.563289] Stack: 0296 810222439400 883e9be0 810222439400 [39943.579846] 802a6728 810222439400 80297e34 [39943.595152] 81004d0a67c0 0017 88401a80 80297f33 [39943.609871] Call Trace: [39943.615566] [802a6728] shrink_dcache_for_umount+0x2f/0x3d [39943.628463] [80297e34] generic_shutdown_super+0x19/0xf1 [39943.641011] [80297f33] kill_anon_super+0x9/0x35 [39943.652193] [883cd1ba] :nfs:nfs_kill_super+0xd/0x16 [39943.664037] [80297fe4] deactivate_super+0x6a/0x83 [39943.675537] [802ab8ab] sys_umount+0x23c/0x24d [39943.686361] [802a5c8a] d_kill+0x40/0x55 [39943.696139] [802a7217] dput+0x26/0x115 [39943.705745] [802970c0] __fput+0x14a/0x179 [39943.715861] [802aabd1] mntput_no_expire+0x1f/0x86 [39943.727375] [802946ea] filp_close+0x5a/0x61 [39943.737853] [8020bfde] system_call+0x7e/0x83 [39943.748495] [39943.751674] [39943.751675] Code: 0f 0b eb fe 48 c7 c7 80 06 63 80 e8 67 75 17 00 48 8b 53 40 [39943.770405] RIP [802a64ce] shrink_dcache_for_umount_subtree+0x16/0x241 [39943.785790] RSP 8101dc88fe18 [82148.423473] JBD: barrier-based sync failed on dm-1 - disabling barriers -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Mon, 3 Dec 2007 16:23:58 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote: > > FYI > > Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, > but they're not changing anything near this AFAIK) > > -Andi > > [101109.104881] [ cut here ] > [101109.114487] kernel BUG at fs/dcache.c:595! > [101109.123053] invalid opcode: [1] SMP > [101109.131492] last sysfs file: > /devices/system/cpu/cpu7/cache/index2/shared_cpu_map > [101109.147023] CPU 0 > [101109.151458] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 > iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 > cpufreq_conserv > ative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd > mbcache loop dm_mod iTCO_wdt e1000 container button rtc_cmos rtc_core > i2c_i801 sh > pchp iTCO_vendor_support i2c_core rtc_lib sr_mod pci_hotplug cdrom sg floppy > ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi > ata_p > iix ahci libata scsi_mod thermal processor > [101109.245056] Pid: 8365, comm: umount.nfs Tainted: G N > 2.6.24-rc3-git3-2-default #1 > [101109.261620] RIP: 0010:[] [] > shrink_dcache_for_umount_subtree+0x16/0x241 > [101109.281862] RSP: 0018:81019294be18 EFLAGS: 00010202 > [101109.299219] RAX: RBX: 81009500ad80 RCX: > > [101109.314048] RDX: RSI: 0296 RDI: > 81009500ad80 > [101109.328868] RBP: 81003679a970 R08: 81007311f510 R09: > 0296 > [101109.343687] R10: 81007311f510 R11: 0400 R12: > 810225719c00 > [101109.358507] R13: R14: 7f3173a7d3f0 R15: > > [101109.373332] FS: 7f31729c56f0() GS:8051b000() > knlGS: > [101109.390081] CS: 0010 DS: ES: CR0: 8005003b > [101109.401934] CR2: 40d4bebc CR3: 0001e61e7000 CR4: > 06e0 > [101109.416761] DR0: DR1: DR2: > > [101109.431600] DR3: DR6: 0ff0 DR7: > 0400 > [101109.446432] Process umount.nfs (pid: 8365, threadinfo 81019294a000, > task 8102250f87e0) > [101109.464203] Stack: 0296 810225719c00 883e9be0 > 810225719c00 > [101109.480929] 802a660c 810225719c00 > 80297d34 > [101109.496407] 81007311f480 0017 88401e90 > 80297e33 > [101109.511304] Call Trace: > [101109.517158] [] shrink_dcache_for_umount+0x2f/0x3d > [101109.530218] [] generic_shutdown_super+0x19/0xf1 > [101109.542941] [] kill_anon_super+0x9/0x35 > [101109.554281] [] :nfs:nfs_kill_super+0xd/0x16 > [101109.566301] [] deactivate_super+0x6a/0x83 > [101109.577988] [] sys_umount+0x23c/0x24d > [101109.588979] [] d_kill+0x40/0x55 > [101109.598919] [] dput+0x26/0x115 > [101109.608684] [] __fput+0x14a/0x179 > [101109.618987] [] mntput_no_expire+0x1f/0x86 > [101109.630671] [] filp_close+0x5a/0x61 > [101109.641307] [] system_call+0x7e/0x83 > [101109.652126] > [101109.655477] > [101109.655478] Code: 0f 0b eb fe 48 c7 c7 80 f6 62 80 e8 eb 70 17 00 48 8b > 53 40 > [101109.674552] RIP [] > shrink_dcache_for_umount_subtree+0x16/0x241 > [101109.690110] RSP > wth? sb->s_root->d_parent != sb->s_root. Is it repeatable? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
On Mon, 3 Dec 2007 16:23:58 +0100 Andi Kleen [EMAIL PROTECTED] wrote: FYI Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, but they're not changing anything near this AFAIK) -Andi [101109.104881] [ cut here ] [101109.114487] kernel BUG at fs/dcache.c:595! [101109.123053] invalid opcode: [1] SMP [101109.131492] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [101109.147023] CPU 0 [101109.151458] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conserv ative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod iTCO_wdt e1000 container button rtc_cmos rtc_core i2c_i801 sh pchp iTCO_vendor_support i2c_core rtc_lib sr_mod pci_hotplug cdrom sg floppy ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_p iix ahci libata scsi_mod thermal processor [101109.245056] Pid: 8365, comm: umount.nfs Tainted: G N 2.6.24-rc3-git3-2-default #1 [101109.261620] RIP: 0010:[802a63b2] [802a63b2] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.281862] RSP: 0018:81019294be18 EFLAGS: 00010202 [101109.299219] RAX: RBX: 81009500ad80 RCX: [101109.314048] RDX: RSI: 0296 RDI: 81009500ad80 [101109.328868] RBP: 81003679a970 R08: 81007311f510 R09: 0296 [101109.343687] R10: 81007311f510 R11: 0400 R12: 810225719c00 [101109.358507] R13: R14: 7f3173a7d3f0 R15: [101109.373332] FS: 7f31729c56f0() GS:8051b000() knlGS: [101109.390081] CS: 0010 DS: ES: CR0: 8005003b [101109.401934] CR2: 40d4bebc CR3: 0001e61e7000 CR4: 06e0 [101109.416761] DR0: DR1: DR2: [101109.431600] DR3: DR6: 0ff0 DR7: 0400 [101109.446432] Process umount.nfs (pid: 8365, threadinfo 81019294a000, task 8102250f87e0) [101109.464203] Stack: 0296 810225719c00 883e9be0 810225719c00 [101109.480929] 802a660c 810225719c00 80297d34 [101109.496407] 81007311f480 0017 88401e90 80297e33 [101109.511304] Call Trace: [101109.517158] [802a660c] shrink_dcache_for_umount+0x2f/0x3d [101109.530218] [80297d34] generic_shutdown_super+0x19/0xf1 [101109.542941] [80297e33] kill_anon_super+0x9/0x35 [101109.554281] [883cd1ba] :nfs:nfs_kill_super+0xd/0x16 [101109.566301] [80297ee4] deactivate_super+0x6a/0x83 [101109.577988] [802ab78f] sys_umount+0x23c/0x24d [101109.588979] [802a5b6e] d_kill+0x40/0x55 [101109.598919] [802a70fb] dput+0x26/0x115 [101109.608684] [80296fc0] __fput+0x14a/0x179 [101109.618987] [802aaab5] mntput_no_expire+0x1f/0x86 [101109.630671] [802945ea] filp_close+0x5a/0x61 [101109.641307] [8020bfde] system_call+0x7e/0x83 [101109.652126] [101109.655477] [101109.655478] Code: 0f 0b eb fe 48 c7 c7 80 f6 62 80 e8 eb 70 17 00 48 8b 53 40 [101109.674552] RIP [802a63b2] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.690110] RSP 81019294be18 wth? sb-s_root-d_parent != sb-s_root. Is it repeatable? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
FYI Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, but they're not changing anything near this AFAIK) -Andi [101109.104881] [ cut here ] [101109.114487] kernel BUG at fs/dcache.c:595! [101109.123053] invalid opcode: [1] SMP [101109.131492] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [101109.147023] CPU 0 [101109.151458] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conserv ative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod iTCO_wdt e1000 container button rtc_cmos rtc_core i2c_i801 sh pchp iTCO_vendor_support i2c_core rtc_lib sr_mod pci_hotplug cdrom sg floppy ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_p iix ahci libata scsi_mod thermal processor [101109.245056] Pid: 8365, comm: umount.nfs Tainted: G N 2.6.24-rc3-git3-2-default #1 [101109.261620] RIP: 0010:[] [] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.281862] RSP: 0018:81019294be18 EFLAGS: 00010202 [101109.299219] RAX: RBX: 81009500ad80 RCX: [101109.314048] RDX: RSI: 0296 RDI: 81009500ad80 [101109.328868] RBP: 81003679a970 R08: 81007311f510 R09: 0296 [101109.343687] R10: 81007311f510 R11: 0400 R12: 810225719c00 [101109.358507] R13: R14: 7f3173a7d3f0 R15: [101109.373332] FS: 7f31729c56f0() GS:8051b000() knlGS: [101109.390081] CS: 0010 DS: ES: CR0: 8005003b [101109.401934] CR2: 40d4bebc CR3: 0001e61e7000 CR4: 06e0 [101109.416761] DR0: DR1: DR2: [101109.431600] DR3: DR6: 0ff0 DR7: 0400 [101109.446432] Process umount.nfs (pid: 8365, threadinfo 81019294a000, task 8102250f87e0) [101109.464203] Stack: 0296 810225719c00 883e9be0 810225719c00 [101109.480929] 802a660c 810225719c00 80297d34 [101109.496407] 81007311f480 0017 88401e90 80297e33 [101109.511304] Call Trace: [101109.517158] [] shrink_dcache_for_umount+0x2f/0x3d [101109.530218] [] generic_shutdown_super+0x19/0xf1 [101109.542941] [] kill_anon_super+0x9/0x35 [101109.554281] [] :nfs:nfs_kill_super+0xd/0x16 [101109.566301] [] deactivate_super+0x6a/0x83 [101109.577988] [] sys_umount+0x23c/0x24d [101109.588979] [] d_kill+0x40/0x55 [101109.598919] [] dput+0x26/0x115 [101109.608684] [] __fput+0x14a/0x179 [101109.618987] [] mntput_no_expire+0x1f/0x86 [101109.630671] [] filp_close+0x5a/0x61 [101109.641307] [] system_call+0x7e/0x83 [101109.652126] [101109.655477] [101109.655478] Code: 0f 0b eb fe 48 c7 c7 80 f6 62 80 e8 eb 70 17 00 48 8b 53 40 [101109.674552] RIP [] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.690110] RSP -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG fs/dcache.c:595 in 2.4.24rc3-git3 during NFS umount
FYI Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches, but they're not changing anything near this AFAIK) -Andi [101109.104881] [ cut here ] [101109.114487] kernel BUG at fs/dcache.c:595! [101109.123053] invalid opcode: [1] SMP [101109.131492] last sysfs file: /devices/system/cpu/cpu7/cache/index2/shared_cpu_map [101109.147023] CPU 0 [101109.151458] Modules linked in: nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables ip6table_filter ip6_tables x_tables af_packet ipv6 cpufreq_conserv ative cpufreq_userspace cpufreq_powersave acpi_cpufreq dm_crypt ext2 ext3 jbd mbcache loop dm_mod iTCO_wdt e1000 container button rtc_cmos rtc_core i2c_i801 sh pchp iTCO_vendor_support i2c_core rtc_lib sr_mod pci_hotplug cdrom sg floppy ehci_hcd uhci_hcd sd_mod usbcore edd reiserfs fan aic79xx scsi_transport_spi ata_p iix ahci libata scsi_mod thermal processor [101109.245056] Pid: 8365, comm: umount.nfs Tainted: G N 2.6.24-rc3-git3-2-default #1 [101109.261620] RIP: 0010:[802a63b2] [802a63b2] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.281862] RSP: 0018:81019294be18 EFLAGS: 00010202 [101109.299219] RAX: RBX: 81009500ad80 RCX: [101109.314048] RDX: RSI: 0296 RDI: 81009500ad80 [101109.328868] RBP: 81003679a970 R08: 81007311f510 R09: 0296 [101109.343687] R10: 81007311f510 R11: 0400 R12: 810225719c00 [101109.358507] R13: R14: 7f3173a7d3f0 R15: [101109.373332] FS: 7f31729c56f0() GS:8051b000() knlGS: [101109.390081] CS: 0010 DS: ES: CR0: 8005003b [101109.401934] CR2: 40d4bebc CR3: 0001e61e7000 CR4: 06e0 [101109.416761] DR0: DR1: DR2: [101109.431600] DR3: DR6: 0ff0 DR7: 0400 [101109.446432] Process umount.nfs (pid: 8365, threadinfo 81019294a000, task 8102250f87e0) [101109.464203] Stack: 0296 810225719c00 883e9be0 810225719c00 [101109.480929] 802a660c 810225719c00 80297d34 [101109.496407] 81007311f480 0017 88401e90 80297e33 [101109.511304] Call Trace: [101109.517158] [802a660c] shrink_dcache_for_umount+0x2f/0x3d [101109.530218] [80297d34] generic_shutdown_super+0x19/0xf1 [101109.542941] [80297e33] kill_anon_super+0x9/0x35 [101109.554281] [883cd1ba] :nfs:nfs_kill_super+0xd/0x16 [101109.566301] [80297ee4] deactivate_super+0x6a/0x83 [101109.577988] [802ab78f] sys_umount+0x23c/0x24d [101109.588979] [802a5b6e] d_kill+0x40/0x55 [101109.598919] [802a70fb] dput+0x26/0x115 [101109.608684] [80296fc0] __fput+0x14a/0x179 [101109.618987] [802aaab5] mntput_no_expire+0x1f/0x86 [101109.630671] [802945ea] filp_close+0x5a/0x61 [101109.641307] [8020bfde] system_call+0x7e/0x83 [101109.652126] [101109.655477] [101109.655478] Code: 0f 0b eb fe 48 c7 c7 80 f6 62 80 e8 eb 70 17 00 48 8b 53 40 [101109.674552] RIP [802a63b2] shrink_dcache_for_umount_subtree+0x16/0x241 [101109.690110] RSP 81019294be18 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
