From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966178AbcBCTPR (ORCPT ); Wed, 3 Feb 2016 14:15:17 -0500 Received: from mail-yk0-f174.google.com ([209.85.160.174]:33647 "EHLO mail-yk0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965337AbcBCTPP (ORCPT ); Wed, 3 Feb 2016 14:15:15 -0500 Date: Wed, 3 Feb 2016 14:15:13 -0500 From: Tejun Heo To: Thomas Gleixner Cc: Michal Hocko , Jiri Slaby , Petr Mladek , Jan Kara , Ben Hutchings , Sasha Levin , Shaohua Li , LKML , stable@vger.kernel.org, Daniel Bilik Subject: Re: Crashes with 874bbfe600a6 in 3.18.25 Message-ID: <20160203191513.GN14091@mtj.duckdns.org> 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> <20160203190159.GM14091@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 03, 2016 at 08:05:57PM +0100, Thomas Gleixner wrote: > > Well, you're in an unnecessary escalation mode as usual. Was the > > attitude really necessary? Chill out and read the thread again. > > Michal is saying the dwork->cpu assignment was bogus and I was > > refuting that. > > Right, but at the same time you could have admitted, that the current state is > buggy and needs a sanity check in unbound_pwq_by_node(). It's crashing. Of course it's buggy. The main discussion on the bug was on the other thread and I was trying to put out the confusions posted on this thread. > > Michal brought it up here but there's a different thread where Mike > > reported NUMA_NO_NODE issue and I already posted the fix. > > > > http://lkml.kernel.org/g/20160203185425.GK14091@mtj.duckdns.org > > 5 minute ago w/o cc'ing the people who participated in that discussion. Yeah, I got to the thread this morning and got your email right after sending out the patch. I don't know. The handling of this wasn't out of the norm. I asked this multiple times but let me try again. Can we please try to stay civil and technical? There are times where escalation is necessary but this one was gratuitous. Thanks. -- tejun