netstat and lsof both crawl /proc//fd to associate processes to ports/sockets, and /proc//fd doesn't get populated for kernel threads AFAIK.
lockd is always a kernel thread - at least on modern (newer than say 2.2) kernels.
netstat and lsof both crawl /proc//fd to associate processes to ports/sockets, and /proc//fd doesn't get populated for kernel threads AFAIK.
lockd is always a kernel thread - at least on modern (newer than say 2.2) kernels.