linux-kernel - Re: [PATCH] proc: let task status file print utime and stime.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 19 Aug 2009 01:27:55 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Amerigo Wang <xiyou.wangcong@...il.com>
Cc:	kosaki.motohiro@...fujitsu.com,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Tatsuhiro Aoshima <tatsu.pc@...il.com>,
	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>,
	albert@...rs.sf.net
Subject: Re: [PATCH] proc: let task status file print utime and stime.

Hi

> On Mon, Aug 17, 2009 at 03:32:53PM +0900, KAMEZAWA Hiroyuki wrote:
> >On Mon, 17 Aug 2009 14:32:02 +0800
> >Amerigo Wang <xiyou.wangcong@...il.com> wrote:
> >
> >> On Mon, Aug 17, 2009 at 03:22:06PM +0900, KAMEZAWA Hiroyuki wrote:
> >> >On Mon, 17 Aug 2009 14:18:21 +0800
> >> >Amerigo Wang <xiyou.wangcong@...il.com> wrote:
> >> >
> >> >> Ah... in fact, I expected 'ps' can report this, however, surprisingly
> >> >> it doesn't have this, at least not what I expect (unless I miss
> >> >> something obvious).

Yes, hehe, I also expected so :-)



> >> >> >In another thinking, in old days, /proc/<pid>/stat was enough because most of
> >> >> >users uses scanf() or some C langage to read fixed-format data.
> >> >> >/proc/<pid>/status is useful for some script languages which has 
> >> >> >good parser per line. 
> >> >> 
> >> >> Well... I think this work should be left to 'ps', e.g.
> >> >> 
> >> >>   ps -o pid,utime,stime
> >> >> 
> >> >> 'ps' is responsible to read /proc/<pid>/stat for the user.
>
> >> >Hmm, personally, I don't like 'ps' and its unified filter.
> >> >
> >> >When I want to know status of a process of PID,
> >> ># ps -o pid,utime,stime  PID
> >> >
> >> >'ps' scans *all* process and filter PID. (try #strace ps)
> >> >I like checking /proc/<pid>/<something> without 'ps' in an environment
> >> >where thousands of processes runs.
> >> 
> >> Sure, we already have '-p' for 'ps', e.g.
> >> 
> >>  ps -p 1 -o pid,user,comm
> >> 
> >> Enjoy. :-)
> >I said it's verrrrry slow.
>
> 
> Hmm, for me it looks like that 'ps' should be fixed...
> 
> I haven't checked the source code of 'ps', but I don't think
> this is O(n) if '-p' is specified. If we just use something
> like 'test -d /proc/<pid>' it would be O(1).

I think kamezawa-san is right.
procps always read ALL proc. and after, it check pid by want_this_proc().

That's obviously O(n) ;-)

---------------------------------------------------------------
static void simple_spew(void){
(snip)
  switch(thread_flags & (TF_show_proc|TF_loose_tasks|TF_show_task)){
  case TF_show_proc:                   // normal non-thread output
    while(readproc(ptp,&buf)){
      if(want_this_proc(&buf)){
        show_one_proc(&buf, proc_format_list);
      }
      if(buf.cmdline) free((void*)*buf.cmdline); // ought to reuse
      if(buf.environ) free((void*)*buf.environ); // ought to reuse
    }
    break;
---------------------------------------------------------------



> >> Anyway, I would like to see 'ps' to have 'utime,stime' field, on
> >> my machine, its output for 'utime,stime' looks wrong.
> >> 
> >> Maybe we should Cc procps developers?
> >ya, maybe. it's good to be CCed.
> 
> Done. Albert?

Albert? What do you think?



> >BTW, why all other status
> >Name:   cat
> >State:  R (running)
> >Tgid:   7068
> >Pid:    7068
> >PPid:   6115
> >TracerPid:      0
> >Uid:    500     500     500     500
> >Gid:    500     500     500     500
> >FDSize: 256
> >Groups: 500
> >
> >are allowed to be duplicated ?
> 
> 
> I don't know... :( I still prefer to use 'ps'.

Do their have any exclusive relation?




--
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/