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
| ||
|
Date: Thu, 31 Mar 2016 12:58:53 +0200 From: Michal Hocko <mhocko@...nel.org> To: Ingo Molnar <mingo@...nel.org> Cc: Peter Zijlstra <peterz@...radead.org>, Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, "David S. Miller" <davem@...emloft.net>, Tony Luck <tony.luck@...el.com>, Chris Zankel <chris@...kel.net>, Max Filippov <jcmvbkbc@...il.com>, x86@...nel.org, linux-alpha@...r.kernel.org, linux-ia64@...r.kernel.org, linux-s390@...r.kernel.org, linux-sh@...r.kernel.org, sparclinux@...r.kernel.org, linux-xtensa@...ux-xtensa.org, linux-arch@...r.kernel.org Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore On Thu 31-03-16 11:20:05, Ingo Molnar wrote: > > * Michal Hocko <mhocko@...nel.org> wrote: > > > On Wed 30-03-16 15:32:17, Peter Zijlstra wrote: > > > On Mon, Feb 29, 2016 at 01:58:14PM +0100, Michal Hocko wrote: > > > > I have tested on x86 with OOM situations with high mmap_sem contention > > > > (basically many parallel page faults racing with many parallel mmap/munmap > > > > tight loops) so the waiters for the write locks are routinely interrupted > > > > by SIGKILL. > > > > > > Aside from the one niggle (as per the other email) they look good to me > > > and I would take them through the tip/locking tree. > > > > Thanks for the review! I understand that tip/locking would be the most > > appropriate place [...] > > Yes. > > > [...] but I am wondering whether this causes some issues with the follow up > > patches which use this new API and which I expect to go via Andrew's tree. > > So AFAIK Andrew's tree is based on top of linux-next, so once it goes into > tip:locking/core, -mm can pick it up as well 1-2 days later. OK. Andrew, just make sure you send the follow up changes to Linus after tip/locking is merged. > Please send the changes in isolation, for merge into the locking tree. Yes, that's what I plan to do in few days. Thanks! -- Michal Hocko SUSE Labs
Powered by blists - more mailing lists