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
| ||
|
Message-ID: <558C1DCE.1010705@kyup.com> Date: Thu, 25 Jun 2015 18:27:10 +0300 From: Nikolay Borisov <kernel@...p.com> To: Michal Hocko <mhocko@...e.cz> CC: Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org, Marian Marinov <mm@...com> Subject: Re: Lockup in wait_transaction_locked under memory pressure On 06/25/2015 06:18 PM, Michal Hocko wrote: > On Thu 25-06-15 17:34:22, Nikolay Borisov wrote: >> On 06/25/2015 05:05 PM, Michal Hocko wrote: >>> On Thu 25-06-15 16:49:43, Nikolay Borisov wrote: >>> [...] >>>> How would you advise to rectify such situation? >>> >>> As I've said. Check the oom victim traces and see if it is holding any >>> of those locks. >> >> As mentioned previously all OOM traces are identical to the one I've >> sent - OOM being called form the page fault path. > > By identical you mean that all of them kill the same task? Or just that > the path is same (which wouldn't be surprising as this is the only path > which triggers memcg oom killer)? The code path is the same, the tasks being killed are different > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists