| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 1 Aug 2007 22:07:54 +0300 From: Rokas Masiulis <roma1390@...is.mif.vu.lt> To: linux-kernel@...r.kernel.org Subject: Examine user space locks Hi sometimes user space program hangs forever. In old days i remeber there was unkillable dosemu. May be there are good how to. Some one can point to it? This is problem/solution isn't related to current kernel. This is question: what to do in this sitaution. Now i have eject(1) $ ps uax | grep eject root 12662 0.0 0.0 1528 560 ? D Jul31 0:00 eject root 12866 0.0 0.0 1532 560 pts/10 D Jul31 0:00 eject $ date Wed Aug 1 21:56:59 EEST 2007 That same eject worked on that same hardware and kernel before. # strace -p 12662 Process 12662 attached - interrupt to quit dosn't show which syscall is called. kill -9 12662 doesn't help to. No ops, no other info in dmesg. How to find problem? How to kill/stop proces without reboot? How to find which lock is taken by kernel to complete user space request/syscalls? kernel: 2.6.17-gentoo-r4-20061014-00 dmesg: http://89.190.108.145/~rokas/dmesg.txt config: http://89.190.108.145/~rokas/config.txt Thanks for any hints. roma139 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists