search for: sys_newstat

...lt;ffffffffaf45d661>] user_path_at+0x11/0x20 [26399.968501]? [<ffffffffaf450343>] vfs_fstatat+0x63/0xc0 [26399.968505]? [<ffffffffaf4506fe>] SYSC_newstat+0x2e/0x60 [26399.968530]? [<ffffffffaf33e3f6>] ? __audit_syscall_exit+0x1e6/0x280 [26399.968534]? [<ffffffffaf450bbe>] SyS_newstat+0xe/0x10 [26399.968544]? [<ffffffffaf98dede>] system_call_fastpath+0x25/0x2a [27479.967352] INFO: task cp:4656 blocked for more than 120 seconds. [27479.967414] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [27479.967711] cp????????????? D ffff8936b65...

...or not.The race could occur between stat system call and writeback kernel thread. The lines are fs/btrfs/inode.c 5422 fs/btrfs/inode.c 1378 The stack traces are For file line fs/btrfs/inode.c 5422 btrfs_getattr+0x141/0x15e vfs_getattr+0x47/0xf4 vfs_fstatat+0x43/0x5a vfs_stat+0x16/0x18 sys_newstat+0x3d/0x75 system_call_fastpath+0x16/0x1b And for file line fs/btrfs/inode.c 1378 btrfs_clear_bit_hook+0xcc1/0x10f2 clear_state_bit+0x4db/0xa89 clear_extent_bit+0x9e1/0xc86 extent_clear_unlock_delalloc+0x8c/0x1d8 cow_file_range+0x1356/0x1432 run_delalloc_range+0x263/0x1702 __extent...

...wall_time+18/72] Aug 16 11:33:15 asc_server kernel: [cprt+9024/38422] [grow_inodes+32/428] [get_new_inode+197/304] [iget+103/116] [ext2_lookup+90/140] [real_lookup+91/180] [do_select+487/512] [lookup_dentry+304/504] Aug 16 11:33:15 asc_server kernel: [getname+95/156] [__namei+49/104] [sys_newstat+20/116] [system_call+52/64] Aug 16 11:33:15 asc_server kernel: Code: 89 50 04 89 02 5b 83 c4 18 c3 89 f6 83 ec 18 53 8b 5c 24 20 ... /var/log/messages ... Aug 16 11:30:01 asc_server -- MARK -- Aug 16 11:33:14 asc_server kernel: Unable to handle kernel NULL pointer dereference at virtual address 0...

...x2f1 Mar 8 03:33:23 web1 kernel: [<ffffffff80012851>] getname+0x15b/0x1c2 Mar 8 03:33:23 web1 kernel: [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c Mar 8 03:33:23 web1 kernel: [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a Mar 8 03:33:23 web1 kernel: [<ffffffff80023703>] sys_newstat+0x19/0x31 Mar 8 03:33:23 web1 kernel: [<ffffffff8005d116>] system_call+0x7e/0x83 If anyone has some advice on where to go from here it would be greatly appreciated. Thanks in advance. -- PJF

...alk+0x42/0xb2 [<ffffffff8000cd72>] do_path_lookup+0x275/0x2f1 [<ffffffff80012851>] getname+0x15b/0x1c2 [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 [<ffffffff80023703>] sys_newstat+0x19/0x31 [<ffffffff8005d229>] tracesys+0x71/0xe0 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc RIP [<ffff8100dc435cf0>] RSP <ffff81001529fd18> CR2: ffff8100dc435cf0 <0>Kernel panic - not syncing: Fatal...

...e_fault+0x1aa/0x3c0 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff81156f2d>] ? cp_new_stat+0x10d/0x120 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff81157021>] ? vfs_fstatat+0x41/0x80 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff8115715f>] ? sys_newstat+0x1f/0x50 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff817ecee2>] ? system_call_fastpath+0x16/0x1b Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] Code: b6 44 24 18 4c 89 e7 83 e0 80 3c 01 19 db e8 76 3f 00 00 f7 d3 83 e3 a1 89 d8 5b 5d 41 5c c3 0f 0b eb fe 0f 0b eb fe 0f 0$ Jul...

...aruman kernel: [<ffffffff85a24cd3>] vfs_fstatat+0x63/0xc0 Oct 26 09:11:45 saruman kernel: [<ffffffff85a2523e>] SYSC_newstat+0x2e/0x60 Oct 26 09:11:45 saruman kernel: [<ffffffff859326b6>] ? __audit_syscall_exit+0x1e6/0x280 Oct 26 09:11:45 saruman kernel: [<ffffffff85a2551e>] SyS_newstat+0xe/0x10 Oct 26 09:11:45 saruman kernel: [<ffffffff85f2579b>] system_call_fastpath+0x22/0x27 Oct 26 09:11:50 saruman systemd: Unmounting NAS1 share 1... Oct 26 09:11:50 saruman systemd: Unmounted NAS1 share 1. Oct 26 09:12:41 saruman systemd: dovecot.service stop-final-sigterm timed out. Ki...

...etname+0x15b/0x1c1 [<ffffffff8028ff52>] __user_walk_fd+0x37/0x4c [<ffffffff80288883>] vfs_stat_fd+0x1b/0x4a [<ffffffff80219b90>] do_page_fault+0xee9/0x1215 [<ffffffff8027e38d>] fd_install+0x25/0x5f [<ffffffff80239287>] do_sigaction+0x7a/0x1f3 [<ffffffff80288a4e>] sys_newstat+0x19/0x31 [<ffffffff80239495>] sys_rt_sigaction+0x59/0x98 [<ffffffff8020ab73>] error_exit+0x0/0x71 [<ffffffff8020a436>] system_call+0x86/0x8b [<ffffffff8020a3b0>] system_call+0x0/0x8b ************* these are basic debian etch brand new set ups, they have nothing else th...

> > But if I start the automount unit and ls the mount point, the shell hangs > and eventually, a long time later (I haven't timed it, maybe an hour), I > eventually get a prompt again. Control-C won't interrupt it. I can still > ssh in and get another session so it's just the process that's accessing > the mount point that hangs. > I don't have a

..._path_at_empty+0x47/0x7b Jul 19 06:25:21 placka kernel: [207743.756056] [<ffffffff810fe28d>] ? cp_new_stat+0xe6/0xfa Jul 19 06:25:21 placka kernel: [207743.756056] [<ffffffff810fe45a>] ? vfs_fstatat+0x32/0x60 Jul 19 06:25:21 placka kernel: [207743.756056] [<ffffffff810fe590>] ? sys_newstat+0x12/0x2b Jul 19 06:25:21 placka kernel: [207743.756056] [<ffffffff81355592>] ? system_call_fastpath+0x16/0x1b Jul 19 06:25:21 placka kernel: [207743.756056] Code: 8b 7b 38 44 89 e2 81 e6 ff ff f9 ff e8 28 fe ff ff 48 85 c0 48 89 c2 75 0f e9 0d 01 00 00 49 63 d7 44 03 7b 40 4c 01 f2 4d 63 ff...