From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754267AbbBAUVJ (ORCPT ); Sun, 1 Feb 2015 15:21:09 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58956 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754134AbbBAUVH (ORCPT ); Sun, 1 Feb 2015 15:21:07 -0500 Date: Sun, 1 Feb 2015 21:19:15 +0100 From: Oleg Nesterov To: Linus Torvalds Cc: Peter Zijlstra , "Rafael J. Wysocki" , Ingo Molnar , Peter Hurley , Davidlohr Bueso , Bruno =?iso-8859-1?Q?Pr=E9mont?= , Linux Kernel Mailing List , Thomas Gleixner , Ilya Dryomov , Mike Galbraith Subject: Re: Linux 3.19-rc5 Message-ID: <20150201201915.GA31945@redhat.com> References: <1421878320.4903.17.camel@stgolabs.net> <54C02E08.4080405@hurleysoftware.com> <1861286.x5DC37NGWz@vostro.rjw.lan> <20150130154742.GA10547@redhat.com> <20150131201601.GZ2896@worktop.programming.kicks-ass.net> <20150201194306.GA29993@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/01, Linus Torvalds wrote: > > On Sun, Feb 1, 2015 at 11:43 AM, Oleg Nesterov wrote: > > > > And personally I agree. sched_annotate_sleep() looks self-documented, it > > is clear that it is used to suppress the warning. > > But *that's not the problem*. > > If it was just silencing the warning, things would be fine. > > But it is actively screwing task state up, and actually changing > behavior of the kernel (in a very subtle part of the code too), and > doing so in ways that potentially introduce WORSE BUGS THAN THE WHOLE > DAMN DEBUG SUPPORT WAS SUPPOSED TO FIND IN THE FIRST PLACE. I understand, that is why I suggested to change it. > I like your patch, but I'm going to combine it with mine that actually > fixes a real bug, Sure, I agree. > because what you don't see in that patch of yours: > ... > > > is that the whole "if (WARN_ONCE()" remains horribly buggy, because of > the line that follows it: > > __set_current_state(TASK_RUNNING); > > in the if-statement. Ah. I just forgot to mention that this change should be rediffed on top of your patch, of course it is not enough. > I'll just combine it with yours to avoid extra noise in this area, and > mark you as the author, fixing *both* of the incorrect state changes. > Ok? Please combine them, but don't mark me as an author, I do not want to take the false credits ;) Oleg.