search for: __d_lookup

Displaying 12 results from an estimated 12 matches for "__d_lookup".

2006 Jan 02
1
2.6.15-rc6 OOPS
...998db100 003d099f c0300b20 f7aee530 > kernel: f7aee658 f71a63e0 f71a63e8 00000292 f7aee530 c02ba525 00000001 f7aee530 > kernel: Call Trace: > kernel: [<c02ba525>] __down+0x75/0xe0 > kernel: [<c0118d70>] default_wake_function+0x0/0x10 > kernel: [<c0172804>] __d_lookup+0xa4/0x110 > kernel: [<c02b8e8f>] __down_failed+0x7/0xc > kernel: [<c016bb42>] .text.lock.namei+0x8/0x1e6 > kernel: [<c0167f35>] do_lookup+0x85/0x90 > kernel: [<c016872f>] __link_path_walk+0x7ef/0xdd0 > kernel: [<c0168d5e>] link_path_walk+0x4e/0xd0...
2014 Jul 01
3
corruption of in-memory data detected (xfs)
...lt;ffffffff802230e6>] __up_read+0x19/0x7f [2870477.695764]? [<ffffffff8824f8f4>] :xfs:xfs_iunlock+0x57/0x79 [2870477.695776]? [<ffffffff80264929>] _spin_lock_irqsave+0x9/0x14 [2870477.695784]? [<ffffffff802230e6>] __up_read+0x19/0x7f [2870477.695791]? [<ffffffff80209f4c>] __d_lookup+0xb0/0xff [2870477.695803]? [<ffffffff8020cd4a>] _atomic_dec_and_lock+0x39/0x57 [2870477.695814]? [<ffffffff8022d6db>] mntput_no_expire+0x19/0x89 [2870477.695829]? [<ffffffff80264929>] _spin_lock_irqsave+0x9/0x14 [2870477.695837]? [<ffffffff802230e6>] __up_read+0x19/0x7f [28...
2006 Sep 01
0
Kernel OOPS with xen 3.0.2 on dom0
...31 08:15:32 mariscal kernel: [<f4a43de6>] xfs_create+0x3b6/0x710 [xfs] Aug 31 08:15:32 mariscal kernel: [<f4a4dc27>] linvfs_mknod+0x217/0x430 [xfs] Aug 31 08:15:32 mariscal kernel: [<f4a0ada4>] xfs_da_do_buf+0x894/0x970 [xfs] Aug 31 08:15:32 mariscal kernel: [<c017f598>] __d_lookup+0x88/0x110 Aug 31 08:15:32 mariscal kernel: [<c017f598>] __d_lookup+0x88/0x110 Aug 31 08:15:32 mariscal kernel: [<f4a3a818>] xfs_trans_unlocked_item+0x38/0x60 [xfs] Aug 31 08:15:32 mariscal kernel: [<f4a4070f>] xfs_access+0x3f/0x50 [xfs] Aug 31 08:15:32 mariscal kernel: [<...
2012 Mar 27
1
Odd hang on a 5.6 system
...k_change+0x13/0x3b Mar 27 16:52:05 cjcsrv kernel: [<e88ddfe4>] cdrom_open+0x833/0x876 [cdrom] Mar 27 16:52:05 cjcsrv kernel: [<c04c95c3>] avc_has_perm+0x3c/0x46 Mar 27 16:52:05 cjcsrv kernel: [<c04c95c3>] avc_has_perm+0x3c/0x46 Mar 27 16:52:05 cjcsrv kernel: [<c048c42f>] __d_lookup+0x98/0xdb Mar 27 16:52:05 cjcsrv kernel: [<c04c95c3>] avc_has_perm+0x3c/0x46 Mar 27 16:52:05 cjcsrv kernel: [<c04c9c29>] inode_has_perm+0x54/0x5c Mar 27 16:52:05 cjcsrv kernel: [<c04eef8a>] kobject_get+0xf/0x13 Mar 27 16:52:05 cjcsrv kernel: [<c04e5e51>] get_disk+0x35/0x...
2007 Nov 21
0
iptables and BUG: soft lockup detected
...[<c0406406>] do_IRQ+0xa5/0xae [<e09aadbb>] do_ipt_set_ctl+0xee/0x607 [ip_tables] [<c0453dfd>] get_page_from_freelist+0x2a6/0x310 [<c05b94bc>] nf_sockopt+0xac/0xda [<c05b950e>] nf_setsockopt+0x11/0x16 [<c05c375f>] ip_setsockopt+0x9fe/0xa1d [<c047e1cb>] __d_lookup+0x98/0xdb [<c0475bc4>] do_lookup+0x53/0x157 [<c04db822>] _atomic_dec_and_lock+0x2a/0x44 [<c0482140>] mntput_no_expire+0x11/0x6a [<c0477e37>] __link_path_walk+0xd11/0xd33 [<c0480a65>] touch_atime+0x60/0x8f [<c04049bf>] apic_timer_interrupt+0x1f/0x24 [<c0...
2011 Jan 12
4
a nasty kernel oops
...erface+0x34/0x6a [<c055e859>] __device_release_driver+0x7d/0xbb [<c055ea91>] device_release_driver+0x1c/0x2b [<c0588351>] usb_driver_release_interface+0x38/0x60 [<c0590cc0>] proc_ioctl_default+0x10d/0x1d0 [<c0591ffd>] usbdev_ioctl+0x1027/0x10de [<c048b06b>] __d_lookup+0x98/0xdb [<c04c7eff>] inode_has_perm+0x54/0x5c [<c04c78ab>] avc_has_perm+0x3c/0x46 [<c04c7eff>] inode_has_perm+0x54/0x5c [<c0464c32>] __handle_mm_fault+0x463/0xaac [<c0486290>] do_ioctl+0x47/0x5d [<c04867f9>] vfs_ioctl+0x47b/0x4d3 [<c0486899>] sys_i...
2007 Dec 11
2
lustre + nfs + alphas
...8:46:33 cpu3 kernel: [<ffffffff887a4ab7>] :mdc:mdc_unlink+0x307/0x3d0 Dec 11 18:46:33 cpu3 kernel: [<ffffffff801405f7>] __next_cpu+0x19/0x28 Dec 11 18:46:33 cpu3 kernel: [<ffffffff80087090>] find_busiest_group+0x20d/0x621 Dec 11 18:46:33 cpu3 kernel: [<ffffffff80009499>] __d_lookup+0xb0/0xff Dec 11 18:46:33 cpu3 kernel: [<ffffffff8886ced6>] :lustre:ll_unlink+0x1d6/0x370 Dec 11 18:46:33 cpu3 kernel: [<ffffffff8883b791>] :lustre:ll_inode_permission+0xa1/0xc0 Dec 11 18:46:33 cpu3 kernel: [<ffffffff80047fc8>] vfs_unlink+0xc2/0x108 Dec 11 18:46:33 cpu3 kernel:...
2008 Jan 28
2
dovecot servers hanging with fuse/glusterfs errors
...6>] __link_path_walk+0xdf2/0xf3c [<ffffffff80261275>] __do_page_cache_readahead+0x8a/0x28f [<ffffffff8802249f>] :fuse:fuse_dentry_revalidate+0x94/0x120 [<ffffffff80299838>] mntput_no_expire+0x19/0x8b [<ffffffff8028f2f3>] link_path_walk+0xd3/0xe5 [<ffffffff8029571e>] __d_lookup+0xb0/0xff [<ffffffff8028ca92>] do_lookup+0x13d/0x173 [<ffffffff8028e687>] __link_path_walk+0x3a3/0xf3c [<ffffffff8028f27c>] link_path_walk+0x5c/0xe5 [<ffffffff80219b90>] do_page_fault+0xee9/0x1215 [<ffffffff8027e38d>] fd_install+0x25/0x5f [<ffffffff8025daac>] fil...
2008 Feb 04
32
Luster clients getting evicted
on our cluster that has been running lustre for about 1 month. I have 1 MDT/MGS and 1 OSS with 2 OST''s. Our cluster uses all Gige and has about 608 nodes 1854 cores. We have allot of jobs that die, and/or go into high IO wait, strace shows processes stuck in fstat(). The big problem is (i think) I would like some feedback on it that of these 608 nodes 209 of them have in dmesg
2008 Feb 12
0
Lustre-discuss Digest, Vol 25, Issue 17
...f0>{:ptlrpc:ldlm_completion_ast+0} >>> <ffffffffa044b64b>{:lustre:ll_prepare_mdc_op_data+139} >>> <ffffffffa0418a32>{:lustre:ll_intent_file_open+450} >>> <ffffffffa044ae10>{:lustre:ll_mdc_blocking_ast+0} >>> <ffffffff80192006>{__d_lookup+287} >>> <ffffffffa0419724>{:lustre:ll_file_open+2100} >>> <ffffffffa0428a18>{:lustre:ll_inode_permission+184} >>> <ffffffff80179bdb>{sys_access+349} >>> <ffffffff8017a1ee>{__dentry_open+201} >>> <ffffffff8017a3a...
2010 Mar 02
3
2.6.33 high cpu usage
With the ATI bug I was hitting earlier fixed, only my btrfs partition continues to show high cpu usage for some operations. Rsync, git pull, git checkout and svn up are typicall operations which trigger the high cpu usage. As an example, this perf report is from using git checkout to change to a new branch; the change needed to checkout 208 files out of about 1600 total files. du(1) reports
2008 Apr 14
8
zaptel 1.4.10 regression with TE220B on Proliant DL380 G5 ?
Hi list, After a lot of testing + troubleshooting, I guess I'm observing what I am now calling a regression with zaptel 1.4.10 (is it?) As such I call for peer feedback, before either asking Digium install support or filing a bug. Thanks in advance! System: HP Proliant DL380 G5 with 2x PCI-X + 1x PCIe riser card OS: Centos 5 Kernel: 2.6.18-53.1.14.el5 (also tested under