linux-kernel - Re: [PATCH] Documentation: fix getdelays.c example -l option and segv

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <46C2E189.7040504@linux.vnet.ibm.com>
Date:	Wed, 15 Aug 2007 16:50:41 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Michael Neuling <mikey@...ling.org>
CC:	linux-kernel@...r.kernel.org, akpm@...l.org
Subject: Re: [PATCH] Documentation: fix getdelays.c example -l option and
 segv

<snip>

>> Is this really required? a sleep() in the code. Why do we do multiple
>> send_cmd()'s in the do loop? I'll test and get back.
> 
> I needed to send another command to receive more data.  Without the per
> loop send_cmd, I never got any more stats. 
> 
> Should we receive more data without the additional send_cmd?  I've been
> running with: 
>   ./getdelays -d -p 1 -l
> 

Interesting, we never used -l that way. We used -l to get data for all
exiting tasks

./getdelays -d -l

For the usage you've mentioned, I'd use

while :
do
	sleep 2
	./getdelays -p 1 -d
done

I guess your changes change getdelays and since there are other ways
to obtaining the same data, I'd remove the last bit of changes made
to send the TGID often to get data.

> Mikey
> 
> 


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL
-
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/