linux-kernel - Re: [PATCH] x86_64: fix delayed signals

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 for Android: free password hash cracker in your pocket

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

Message-ID: <48788891.5070905@gmail.com>
Date:	Sat, 12 Jul 2008 13:33:53 +0300
From:	Török Edwin <edwintorok@...il.com>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Roland McGrath <roland@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Elias Oltmanns <eo@...ensachen.de>
Subject: Re: [PATCH] x86_64: fix delayed signals

On 2008-07-12 01:53, Arjan van de Ven wrote:
> On Fri, 11 Jul 2008 11:31:26 -0700 (PDT)
> Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
>   
>> On Fri, 11 Jul 2008, Linus Torvalds wrote:
>>     
>>> Btw, did any of the impacted people test -rc9? Edwin's report is
>>> about -rc2 and -rc8, and one of the things we fixed since -rc8 is
>>> that incorrect and unintentional nr_zones zeroing that effectively
>>> disabled kswapd - and made everybody do synchronous memory freeing
>>> when they wanted to allocate more memory.. That can play havoc with
>>> any interactive stuff.
>>>       
>> Hmm. Edwin's latencytop output includes this (ignoring the _very_ top 
>> entries that are all either CD-ROM media change tests or are
>> interruptible pipe/select things) at the top:
>>
>> 	21 10264428 915514 get_request_wait __make_request
>> generic_make_request submit_bio xfs_submit_ioend_bio xfs_submit_ioend 
>> 		xfs_page_state_convert xfs_vm_writepage __writepage 
>> 		write_cache_pages generic_writepages xfs_vm_writepages
>>     
>
>
> argh. well I guess this might be useful for this case, but normally
> latencytop gives you much more humanly readable data... maybe Edwin
> forgot to do "make install" :-(

I forgot to use 'latencytop -d', I was running latencytop and when I've
seen something interesting I did a 'cat /proc/latency_stats' instead of
'latencytop -d'.
I'll try to use latencytop -d next time.

Best regards,
--Edwin
--
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/