From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754111AbdLNSVN (ORCPT ); Thu, 14 Dec 2017 13:21:13 -0500 Received: from mail.kernel.org ([198.145.29.99]:51838 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753703AbdLNSVM (ORCPT ); Thu, 14 Dec 2017 13:21:12 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 098A4218D1 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Thu, 14 Dec 2017 13:21:09 -0500 From: Steven Rostedt To: Tejun Heo Cc: Petr Mladek , Sergey Senozhatsky , Jan Kara , Andrew Morton , Peter Zijlstra , Rafael Wysocki , Pavel Machek , Tetsuo Handa , linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread Message-ID: <20171214132109.32ae6a74@gandalf.local.home> In-Reply-To: <20171214181153.GZ3919388@devbig577.frc2.facebook.com> References: <20171204134825.7822-1-sergey.senozhatsky@gmail.com> <20171214142709.trgl76hbcdwaczzd@pathway.suse.cz> <20171214152551.GY3919388@devbig577.frc2.facebook.com> <20171214125506.52a7e5fa@gandalf.local.home> <20171214181153.GZ3919388@devbig577.frc2.facebook.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Dec 2017 10:11:53 -0800 Tejun Heo wrote: > Hey, Steven. > > On Thu, Dec 14, 2017 at 12:55:06PM -0500, Steven Rostedt wrote: > > Yes! Please create a reproducer, because I still don't believe there is > > one. And it's all hand waving until there's an actual report that we can > > lock up the system with my approach. > > Yeah, will do, but out of curiosity, Sergey and I already described > what the root problem was and you didn't really seem to take that. Is > that because the explanation didn't make sense to you or us > misunderstanding what your code does? Can you post the message id of the discussion you are referencing. Because I've been swamped with other activities and only been skimming these threads. Thanks, -- Steve