From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Nuno Silva <nuno.silva@vgertech.com>
Cc: Patryk Jakubowski <patrics@interia.pl>, linux-kernel@vger.kernel.org
Subject: Re: Invisible threads in 2.6.9
Date: Wed, 06 Oct 2004 09:50:58 +0200 [thread overview]
Message-ID: <4163A3E2.2060609@stud.feec.vutbr.cz> (raw)
In-Reply-To: <4163619C.4070600@vgertech.com>
Nuno Silva wrote:
> Yes, that's the new method trojans are using to hide tasks... No need to
> install complicated kernel modules anymore :-)
>
> More seriously: That's a problem with current procps utils... They just
> don't show them. I can't complain too much because I'm not doing any
> code, but it would be nice to have a working top...
>
> As a workaround, to at least see the threads without inspecting /proc
> directly, you can use the 'm' and 'H' flags to ps, i.e.
>
> $ ps auwxH
>
It doesn't work for me:
# ps aux | grep [t]hread
michich 7447 0.0 0.0 0 0 pts/1 Zl+ 09:43 0:00 [threadbug] <defunct>
# ps auwxH | grep [t]hread
#
And I can't inspect /proc directly:
# cd /proc/7447
# ls -l
ls: cannot read symbolic link cwd: No such file or directory
ls: cannot read symbolic link root: No such file or directory
ls: cannot read symbolic link exe: No such file or directory
total 0
dr-xr-xr-x 2 root root 0 Oct 6 09:48 attr
-r-------- 1 root root 0 Oct 6 09:48 auxv
-r--r--r-- 1 root root 0 Oct 6 09:44 cmdline
lrwxrwxrwx 1 root root 0 Oct 6 09:48 cwd
-r-------- 1 root root 0 Oct 6 09:48 environ
lrwxrwxrwx 1 root root 0 Oct 6 09:48 exe
dr-x------ 2 root root 0 Oct 6 09:44 fd
-r--r--r-- 1 root root 0 Oct 6 09:48 maps
-rw------- 1 root root 0 Oct 6 09:48 mem
-r--r--r-- 1 root root 0 Oct 6 09:48 mounts
lrwxrwxrwx 1 root root 0 Oct 6 09:48 root
-r--r--r-- 1 root root 0 Oct 6 09:44 stat
-r--r--r-- 1 root root 0 Oct 6 09:48 statm
-r--r--r-- 1 root root 0 Oct 6 09:44 status
dr-xr-xr-x 3 root root 0 Oct 6 09:45 task
-r--r--r-- 1 root root 0 Oct 6 09:48 wchan
# cd task
bash: cd: task: No such file or directory
# ls -l task
ls: task: No such file or directory
# ls -l | grep task
ls: cannot read symbolic link cwd: No such file or directory
ls: cannot read symbolic link root: No such file or directory
ls: cannot read symbolic link exe: No such file or directory
dr-xr-xr-x 3 root root 0 Oct 6 09:45 task
Isn't it strange?
Michal Schmidt
next prev parent reply other threads:[~2004-10-06 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S268296AbUJDTjb/20041004193948Z+2396@vger.kernel.org>
2004-10-05 20:59 ` Invisible threads in 2.6.9 Patryk Jakubowski
2004-10-06 3:08 ` Nuno Silva
2004-10-06 7:50 ` Michal Schmidt [this message]
2004-10-06 10:14 ` Patryk Jakubowski
[not found] ` <20041006110721.GC4380@vana.vc.cvut.cz>
2004-10-06 11:36 ` Patryk Jakubowski
2004-10-06 14:58 ` Chris Friesen
2004-10-07 0:21 Albert Cahalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4163A3E2.2060609@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.com \
--cc=patrics@interia.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.