linux-kernel - Re: khugepaged / firefox going wild in 3.18-rc

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: <alpine.DEB.2.10.1411041559170.2720@chino.kir.corp.google.com>
Date:	Tue, 4 Nov 2014 16:00:38 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Norbert Preining <preining@...ic.at>
cc:	linux-kernel@...r.kernel.org
Subject: Re: khugepaged / firefox going wild in 3.18-rc

On Wed, 5 Nov 2014, Norbert Preining wrote:

> Dear all,
> 
> (please Cc)
> 
> since 3.18-rc started, regularly, but unpredictably, firefox
> (Debian iceweasel) goes completely boom to 100% CPU, and there
> is also a kernel task khugepaged doing the same.
> 
> I need to kill firefox, or better the X session to get it back to normal.
> 
> THe logs don't show any strange output
> 
> top's top process:
> 
> 27021 norbert   20   0 1351536 449868  88788 R 100.4  5.6   4:46.16 iceweasel   
>    35 root      39  19       0      0      0 R 100.0  0.0   2:41.10 khugepaged  
> 
> Switching back to 3.17 does Not* exhibit the same behaviour.
> 
> Is this a bug in Firefox/Iceweasel, or is there something luring in the
> kernel.
> 

If you have the ability to kill your X session, then you presumably are 
able to capture /proc/pid/stack for these pids to see where it is busy.  
It might also be helpful to see how the grep ^thp_ /proc/vmstat and 
grep ^compact_ /proc/vmstat counters change over time.
--
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/