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: <20150625135859.GH17237@dhcp22.suse.cz> Date: Thu, 25 Jun 2015 15:58:59 +0200 From: Michal Hocko <mhocko@...e.cz> To: Nikolay Borisov <kernel@...p.com> Cc: linux-ext4@...r.kernel.org, Marian Marinov <mm@...com> Subject: Re: Lockup in wait_transaction_locked under memory pressure On Thu 25-06-15 16:54:23, Nikolay Borisov wrote: > > > On 06/25/2015 04:45 PM, Michal Hocko wrote: [...] > > memcg oom killer ignores oom_kill_allocating_task so the victim might be > > different from the current task. That means the victim might get stuck > > behind a lock held by somebody else. If the ext4 journaling code depends > > on memcg charges and retry endlessly then the waiters would get stuck as > > well. > > I've patched the cgroup OOM so that it takes into account the > oom_kill_allocating_task. I am not very much keen on this configuration because it behaves very randomly and I am pretty sure it will just paper over the real issue here. -- Michal Hocko SUSE Labs -- 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