Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424354AbdDUTAN (ORCPT ); Fri, 21 Apr 2017 15:00:13 -0400 Received: from mail-io0-f170.google.com ([209.85.223.170]:34369 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1424248AbdDUTAJ (ORCPT ); Fri, 21 Apr 2017 15:00:09 -0400 MIME-Version: 1.0 In-Reply-To: <20170420143033.3nzi6nruqd5s3n7f@techsingularity.net> References: <20170420110042.73d01e0f@redhat.com> <20170420143033.3nzi6nruqd5s3n7f@techsingularity.net> From: Linus Torvalds Date: Fri, 21 Apr 2017 10:52:29 -0700 X-Google-Sender-Auth: brZfn8bHON5Id-pgu4rEvqZsgwA Message-ID: Subject: Re: Heads-up: two regressions in v4.11-rc series To: Mel Gorman Cc: Jesper Dangaard Brouer , Andrew Morton , Frederic Weisbecker , Tariq Toukan , LKML , linux-mm , "netdev@vger.kernel.org" , Peter Zijlstra Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1039 Lines: 21 On Thu, Apr 20, 2017 at 7:30 AM, Mel Gorman wrote: >> The end result was a revert, and this is waiting in AKPMs quilt queue: >> http://ozlabs.org/~akpm/mmots/broken-out/revert-mm-page_alloc-only-use-per-cpu-allocator-for-irq-safe-requests.patch >> > > This was flagged to Andrew that it should go in for either 4.11 or if > there were concerns about how close to the release we are then put it in > for 4.11-stable. At worst, I can do a resubmit to -stable myself after > it gets merged in the next window if it falls between the cracks. This got merged (commit d34b0733b452: "Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests""). The other issue (caused by commit a499a5a14dbd: "sched/cputime: Increment kcpustat directly on irqtime account") is still open. Frederic? Revert? But I guess it's something we can delay for backporting, it's presumably not possible to hit maliciously except on some fast local network attacker just causing an effective DoS. Linus