From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751065AbcBEIdz (ORCPT ); Fri, 5 Feb 2016 03:33:55 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36009 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbcBEIdx (ORCPT ); Fri, 5 Feb 2016 03:33:53 -0500 Message-ID: <1454661229.3545.49.camel@gmail.com> Subject: Re: Crashes with 874bbfe600a6 in 3.18.25 From: Mike Galbraith To: Daniel Bilik Cc: Jan Kara , Thomas Gleixner , Tejun Heo , Michal Hocko , Jiri Slaby , Petr Mladek , Sasha Levin , Shaohua Li , LKML , stable@vger.kernel.org Date: Fri, 05 Feb 2016 09:33:49 +0100 In-Reply-To: <20160205091146.d25db60f5c68229056aad82f@neosystem.cz> References: <20160126093400.GV24938@quack.suse.cz> <20160126111438.GA731@pathway.suse.cz> <56B1C9E4.4020400@suse.cz> <20160203122855.GB6762@dhcp22.suse.cz> <20160203162441.GE14091@mtj.duckdns.org> <1454518913.6148.15.camel@gmail.com> <20160203170652.GI14091@mtj.duckdns.org> <1454580263.3407.114.camel@gmail.com> <20160204112044.GE4956@quack.suse.cz> <20160204173931.4735a8de14fc0bde6c114321@neosystem.cz> <1454640046.3545.8.camel@gmail.com> <20160205091146.d25db60f5c68229056aad82f@neosystem.cz> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-02-05 at 09:11 +0100, Daniel Bilik wrote: > On Fri, 05 Feb 2016 03:40:46 +0100 > Mike Galbraith wrote: > > IMHO you should restore the CC list and re-post. (If I were the > > maintainer of either the workqueue code or 3.18-stable, I'd be highly > > interested in this finding). > > Sorry, I haven't realized tha patch proposed by Thomas is already on its > way to stable. CC restored and re-posting. I don't know where it's at, but where things stand is that it is needed, but when combined with the patch which at least uncovered the fact that it's needed, the two aren't playing well together according to your test result. Given both patches are already in kernels upstream, and presumably Thomas's patch will eventually wander to stable to fix them up, there might be some maintainer interest. -Mike