search for: open_namei

...w_block+0x58/0x80 Dec 11 04:03:56 fendrian kernel: [ext3_find_entry+288/976] ext3_find_entry+0x120/0x3d0 Dec 11 04:03:56 fendrian kernel: [ext3_lookup+41/160] ext3_lookup+0x29/0xa0 Dec 11 04:03:56 fendrian kernel: [__lookup_hash+108/160] __lookup_hash+0x6c/0xa0 Dec 11 04:03:56 fendrian kernel: [open_namei+279/992] open_namei+0x117/0x3e0 Dec 11 04:03:56 fendrian kernel: [filp_open+46/96] filp_open+0x2e/0x60 Dec 11 04:03:56 fendrian kernel: [sys_open+59/112] sys_open+0x3b/0x70 Dec 11 04:03:56 fendrian kernel: [syscall_call+7/11] syscall_call+0x7/0xb Dec 11 04:03:56 fendrian kernel: Daniel --...

...00000000 Call Trace: [<c01179c9>] printk+0x61/0x114 [<c01672a8>] __ext3_std_error+0x30/0x40 [<c0162c0a>] ext3_setattr+0x19a/0x1b0 [<c014b606>] notify_change+0xe6/0x180 [<c013696b>] do_truncate+0x5b/0x78 [<c0142d41>] may_open+0x165/0x17c [<c0143015>] open_namei+0x2bd/0x3d0 [<c013770f>] filp_open+0x3b/0x5c [<c0137a63>] sys_open+0x37/0x78 [<c0108877>] syscall_call+0x7/0xb Code: 80 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 89 44 24 10 8b 44 grabbing to the ext2 partition: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Unable to handle kernel paging re...

...665000 00000000 [ 899.119135] 00000000 00000000 ffffffea d490c3d4 ee2f0000 f6524580 e6665000 ffffff9c [ 899.119146] Call Trace: [ 899.119157] [<c016d44c>] remove_suid+0xc/0x50 [ 899.119172] [<f90f4689>] btrfs_file_write+0x1a9/0x900 [btrfs] [ 899.119222] [<c019cb7a>] open_namei+0x8a/0x640 [ 899.119244] [<c018ffa5>] nameidata_to_filp+0x35/0x40 [ 899.119255] [<c018fa90>] generic_file_open+0x0/0x60 [ 899.119265] [<c0190000>] do_filp_open+0x50/0x60 [ 899.119277] [<c016e56a>] __filemap_fdatawrite_range+0x7a/0xa0 [ 899.119300] [<f90f44e0>...

...e+8cb/a10> Trace; c016bc77 <__jbd_kmalloc+27/80> Trace; c0165874 <start_this_handle+114/150> Trace; c016595c <journal_start+ac/d0> Trace; c0161951 <ext3_create+81/110> Trace; c014239a <vfs_create+10a/160> Trace; c014219d <lookup_hash+8d/c0> Trace; c014253c <open_namei+14c/630> Trace; c014a11c <dput+1c/150> Trace; c0129270 <file_read_actor+0/e0> Trace; c01366e6 <filp_open+36/60> Trace; c0136a34 <sys_open+34/c0> Trace; c0106ffb <system_call+33/38> Code; c0165908 <journal_start+58/d0> 00000000 <_EIP>: Code; c0165908 &l...

...insmod_unix_O/lib/modules/2.4.17/kernel/net/unix/unix.o_M+-1608504/96] [unix:__insmod_unix_O/lib/modules/2.4.17/kernel/net/unix/unix.o_M+-1608260/96] [filldir+174/224] [__mark_inode_dirty+46/160] [update_atime+81/96] [unix:__insmod_unix_O/lib/modules/2.4.17/kernel/net/unix/unix.o_M+-1627672/96] [open_namei+805/1680] [dentry_open+171/400] [kfree_skbmem+12/112] [filldir+0/224] [vfs_readdir+126/208] [filldir+0/224] [sys_getdents+71/160] [filldir+0/224] [system_call+51/56] Code: 0f 0b 5f 58 8b 54 24 24 bb e2 ff ff ff b8 01 00 00 00 f6 42

...e/0xc9 [<ffffffff8024335e>] inode_setattr+0x22/0x104 [<ffffffff88050b2f>] :ext3:ext3_setattr+0x1bd/0x228 [<ffffffff8022ceab>] notify_change+0x145/0x2f3 [<ffffffff802d17af>] do_truncate+0x5e/0x79 [<ffffffff80212f1a>] may_open+0x1d3/0x22f [<ffffffff8021b4ce>] open_namei+0x2c8/0x6ed [<ffffffff80227a14>] do_filp_open+0x1c/0x38 [<ffffffff8021a1b8>] do_sys_open+0x44/0xbe [<ffffffff802602f9>] tracesys+0xab/0xb6 Code: ff 42 08 8b 07 a9 00 00 20 00 75 0a 0f 0b 68 f5 97 03 88 c2 RIP [<ffffffff88037cb0>] :jbd:journal_grab_journal_head+0x25/0x4...

...03c>] mntput_no_expire+0x19/0x89 [<ffffffff8020eeae>] link_path_walk+0xa6/0xb2 [<ffffffff80263a7e>] __mutex_lock_slowpath+0x60/0x9b [<ffffffff80223f33>] __path_lookup_intent_open+0x56/0x97 [<ffffffff80263ac8>] .text.lock.mutex+0xf/0x14 [<ffffffff8021b52d>] open_namei+0xea/0x6d5 [<ffffffff8029cb30>] set_process_cpu_timer+0xc7/0xd2 [<ffffffff80227caa>] do_filp_open+0x1c/0x38 [<ffffffff8021a364>] do_sys_open+0x44/0xbe [<ffffffff802602f9>] tracesys+0xab/0xb6 Monitoring show that in a timeframe of about 3 minutes the load on the sys...

...system anymore. what the rename() syscall does on kernel side is getting memory from the names_cache twice by calling __getname() which gives out the same pointer twice when the kernel is poisoned this way. anyway, it's an ugly bug that needs to get fixed. the bug is most likely in fs/namei.c, open_namei() - at least i fixed my machine here with this: --- linux-2.4.17-orig/fs/namei.c Wed Oct 17 23:46:29 2001 +++ linux-2.4.17-uml/fs/namei.c Fri Feb 8 02:53:36 2002 @@ -1052,6 +1052,11 @@ error = -ENOENT; if (!dentry->d_inode) goto exit_dput; + + error = -EIO; + if (is_bad_inode(dentry->d_inode...

.../0xd33 [<c047d35d>] link_path_walk+0x49/0xbd [<c046f582>] sys_chdir+0x4f/0x57 [<c047d72a>] do_path_lookup+0x20e/0x25e [<c0470daf>] get_empty_filp+0x99/0x15e [<c047dfd7>] __path_lookup_intent_open+0x42/0x72 [<c047e056>] path_lookup_open+0xf/0x13 [<c047e15a>] open_namei+0x7b/0x609 [<c046e8ca>] do_filp_open+0x1c/0x31 [<c046f582>] sys_chdir+0x4f/0x57 [<c046e91d>] do_sys_open+0x3e/0xae [<c046e9ba>] sys_open+0x16/0x18 [<c0404eff>] syscall_call+0x7/0xb ======================= Code: 0c 29 d0 83 e8 18 c1 e8 03 39 c1 74 29 68 d4 22 8a f8 68 8...

...2000 00000000 00000000 00000000 c9be8a60 00000000 f0cbfa78 efc31ea0 f0cbf9c0 c047e75e e6875774 01222222 00000068 45b55d27 00000000 e6875774 Call Trace: <c047e75e> notify_change+0x164/0x300 <c0465388> do_truncate+0x54/0x6c <c047372f> may_open+0x1a8/0x1fc <c04755ad> open_namei+0x24b/0x5c3 <c04666a6> do_filp_open+0x1c/0x31 <c04667ad> do_sys_open+0x3c/0xa9 <c0466847> sys_open+0x16/0x18 <c0403d2f> syscall_call+0x7/0xb Code: fc ff ff ff b1 c0 fc ff ff 68 f2 00 00 00 68 8b 54 be f8 ff 70 10 8b 00 ff b0 b4 00 00 00 68 52 9e be f8 e8 1f e4 85 c7 83...

I had the following spat out by syslog on my (2.4.18-pre7-ac3) mailer / web server: Assertion failure in do_get_write_access() at transaction.c:611: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" One of its partitions froze hard--I've rebooted it, and I have an oops which the BUG() triggered which won't decode at the moment, but I'll sort that one out

...11c/288> Trace; c006f1c0 <ext3_truncate+33c/4c0> Trace; c0025424 <vmtruncate+148/160> Trace; c00589ac <inode_setattr+34/108> Trace; c00701c8 <ext3_setattr+144/190> Trace; c0058bc4 <notify_change+90/13c> Trace; c00398dc <do_truncate+108/1cc> Trace; c004be94 <open_namei+650/7e8> Trace; c003ad70 <filp_open+58/84> Trace; c003b25c <sys_open+4c/fc> Trace; c0003dfc <ret_from_syscall_1+0/b4> Trace; 01819404 Before first symbol Trace; 0180295c Before first symbol Trace; 01803e08 Before first symbol Trace; 01804590 Before first symbol Trace; 01801cf4...

...0] [try_to_free_inodes+190/260] [scsi_old_times_out+0/300] [ext3_getblk+198/568] [grow_inodes+32/428] [cprt+14006/37792] [get_new_inode+197/312] [iget4+117/128] [__brelse+29/192] [iget+22/32] [ext3_lookup+90/140] [real_lookup+91/180] [permission+32/56] [lookup_dentry+304/504] [__fput+74/84] [open_namei+105/776] [fput+70/84] [filp_open+74/264] [filp_open+17/264] [sys_open+63/160] [sys_open+38/160] [system_call+52/56] Code: 8b 47 08 3d 2b 2f c3 a5 0f 85 be 01 00 00 f6 46 05 01 0f 85 May 2 11:32:00 - While issuing an du -sk on an ext3 filesystem. du -sk segfaulted. Unable to handle ker...

...e; c015c98b <start_this_handle+307/3a8> Trace; c015caa3 <journal_start+77/a0> Trace; c0152986 <ext3_notify_change+14a/360> Trace; c0120176 <do_generic_file_read+8d2/8e0> Trace; c0139638 <notify_change+40/64> Trace; c0129067 <do_truncate+5f/ac> Trace; c01329bc <open_namei+474/4d4> Trace; c0129e40 <filp_open+44/f8> Trace; c012a08e <sys_open+36/94> Trace; c010a034 <system_call+34/38> Code; c012c25f <refile_buffer+17/d0> 00000000 <_EIP>: Code; c012c25f <refile_buffer+17/d0> <===== 0: c6 05 00 00 00 00 00 movb $0...

...k+0xa9a/0xea0 Aug 31 08:15:32 mariscal kernel: [<c01840e4>] mntput_no_expire+0x24/0xb0 Aug 31 08:15:32 mariscal kernel: [<c0177931>] link_path_walk+0x71/0xf0 Aug 31 08:15:32 mariscal kernel: [<c0175ab7>] vfs_create+0xc7/0x140 Aug 31 08:15:32 mariscal kernel: [<c0178fc6>] open_namei+0x5d6/0x670 Aug 31 08:15:32 mariscal kernel: [<c016553e>] do_filp_open+0x2e/0x60 Aug 31 08:15:32 mariscal kernel: [<c0165210>] get_unused_fd+0x50/0xb0 Aug 31 08:15:32 mariscal kernel: [<c01655ba>] do_sys_open+0x4a/0xe0 Aug 31 08:15:32 mariscal kernel: [<c016568c>] sys_op...

I got this.. The system was usuable, but not very. If I tried to access the ext3 volume, it would hang. Reboot hung too, complaining about too many open files. Any ideas? I have no idea what triggered it; this is a big file/web/mail server, with all of that on the ext3 volume. And I've never run ksymoops before, but I think I did it right. - Josh Assertion failure in

...0/0x17a Aug 22 04:03:16 wssproxy kernel: [<c0148a15>] file_read_actor+0x0/0xc9 Aug 22 04:03:16 wssproxy kernel: [<c0148c98>] generic_file_aio_read+0x40/0x47 Aug 22 04:03:16 wssproxy kernel: [<c0168a4a>] do_sync_read+0x97/0xc9 Aug 22 04:03:16 wssproxy kernel: [<c0179a94>] open_namei+0x2c5/0x542 Aug 22 04:03:16 wssproxy kernel: [<c0167c76>] filp_open+0x5c/0x70 Aug 22 04:03:16 wssproxy kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d Aug 22 04:03:16 wssproxy kernel: [<c0168b32>] vfs_read+0xb6/0xe2 Aug 22 04:03:16 wssproxy kernel: [<c0168d45>] sy...

...DoyleBrunson kernel: [<c046fa4b>] get_empty_filp+0x99/0x15e Jan 23 12:53:08 DoyleBrunson kernel: [<c047cd07>] __path_lookup_intent_open+0x42/0x72 Jan 23 12:53:08 DoyleBrunson kernel: [<c047cd86>] path_lookup_open+0xf/0x13 Jan 23 12:53:08 DoyleBrunson kernel: [<c047ce8a>] open_namei+0x7b/0x609 Jan 23 12:53:08 DoyleBrunson kernel: [<c046d56a>] do_filp_open+0x1c/0x31 Jan 23 12:53:08 DoyleBrunson kernel: [<c046d5bd>] do_sys_open+0x3e/0xae Jan 23 12:53:08 DoyleBrunson kernel: [<c046d65a>] sys_open+0x16/0x18 Jan 23 12:53:08 DoyleBrunson kernel: [<c0404eff&g...

...lhost kernel: Call Trace: [ext3_reserve_inode_write+50/172] [start_this_handle+284/352] [ext3_mark_inode_dirty+26/52] [ext3_dirty_inode+163/276] [__mark_inode_dirty+50/188] Jul 4 20:53:16 localhost kernel: [update_atime+75/80] [link_path_walk+1029/2328] [sock_recvmsg+61/184] [path_walk+26/28] [open_namei+131/1396] [filp_open+59/92] Jul 4 20:53:16 localhost kernel: [sys_open+59/248] [system_call+51/56] Jul 4 20:53:16 localhost kernel: Jul 4 20:53:16 localhost kernel: Code: f0 ff 8b 94 00 00 00 0f 88 17 15 00 00 6a 00 57 56 e8 f7 f9 Jul 4 20:53:16 localhost kernel: <6>note: XFree86[...

Hi, We are trying to validate Asterisk as a media gateway PRI <-> SIP with two T400P (8 T1s) per box. The first experience with BOX1 (Compaq, 2.53 GHz, 1 Gb RAM) and just one T400P was encouraging - on the load test with 3 T1s worth of calls we had on average 75% idle CPU. Not so with BOX2 (Dell, single 2.6 GHz Xeon, 1 Gb RAM, 2 T400P) and BOX3 (Dell, dual 2.6 GHz Xeon, 2 Gb RAM, 2 T400P,