Subject: kern/1774: Problems with identd/kvm_read
To: None <gnats-bugs@NetBSD.ORG>
From: None <firstname.lastname@example.org>
Date: 11/20/1995 01:37:43
>Synopsis: identd locking in kvm_read/lseek
>Responsible: kern-bug-people (Kernel Bug People)
>Arrival-Date: Sun Nov 19 23:05:00 1995
>Originator: Joao Carlos Mendes Luis
486/DX33, 16Mb memory, NE2000 nic
System: NetBSD gaia.coppe.ufrj.br 1.0 NetBSD 1.0 (GAIA) #2: Fri Nov 3 03:51:06 EDT 1995 email@example.com:/usr/src/sys/arch/i386/compile/GAIA i386
Some times I note high CPU utilization, just to discover some
copies of identd running. System load (loadavg) equals 1 times
n copies, so I think it's in an infinite CPU loop.
When I call GDB and attach to one of these it's locked running
the getbuf function, running kvm_read in the shared lib area.
To be specific, it's locked inside the lseek() function.
Since none of identd.gebuf or lib/libkvm/kvm.c/kvm_read have
changed since on current, maybe this problem persists.
Seens to me a problem on /dev/kmem, in lseek, or even a race
condition with identd and a dying socket.
Don't know. Sometimes it happens, And I can only notice after
days of wasted CPU.