Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751781AbeANLfw (ORCPT + 1 other); Sun, 14 Jan 2018 06:35:52 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:37574 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751060AbeANLfv (ORCPT ); Sun, 14 Jan 2018 06:35:51 -0500 Date: Sun, 14 Jan 2018 12:35:45 +0100 (CET) From: Thomas Gleixner To: Joseph Salisbury cc: vikas.shivappa@linux.intel.com, stable@vger.kernel.org, linux-kernel@vger.kernel.org, ravi.v.shankar@intel.com, tony.luck@intel.com, fenghua.yu@intel.com, peterz@infradead.org, eranian@google.com, ak@linux.intel.com, davidcc@google.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, 1733662@bugs.launchpad.net, "Roderick W. Smith" Subject: Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing In-Reply-To: <84b8d891-6217-f56d-8ec0-313f7eb317c9@canonical.com> Message-ID: References: <84b8d891-6217-f56d-8ec0-313f7eb317c9@canonical.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-1003856413-1515929746=:2371" X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1003856413-1515929746=:2371 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Fri, 12 Jan 2018, Joseph Salisbury wrote: > Hi Vikas, > > A kernel bug report was opened against Ubuntu [0].  After a kernel > bisect, it was found that reverting the following commit resolved this bug: > > commit 24247aeeabe99eab13b798ccccc2dec066dd6f07 > Author: Vikas Shivappa > Date:   Tue Aug 15 18:00:43 2017 -0700 > >     x86/intel_rdt/cqm: Improve limbo list processing > > > The regression was introduced as of v4.14-r1 and still exists with > current mainline.  The trace with v4.15-rc7 is in comment #44[1]. > > I was hoping to get your feedback, since you are the patch author.  Do > you think gathering any additional data will help diagnose this issue, > or would it be best to submit a revert request? That stinks like a use after free. Can you run with KASAN enabled? Thanks, tglx --8323329-1003856413-1515929746=:2371--