From: Oleg Nesterov <oleg@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Ingo Molnar" <mingo@kernel.org>,
"Peter Hurley" <peter@hurleysoftware.com>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ilya Dryomov" <ilya.dryomov@inktank.com>,
"Mike Galbraith" <umgwanakikbuti@gmail.com>
Subject: Re: Linux 3.19-rc5
Date: Sun, 1 Feb 2015 21:19:15 +0100 [thread overview]
Message-ID: <20150201201915.GA31945@redhat.com> (raw)
In-Reply-To: <CA+55aFw6JzP0uDAwVEvN_AhgSq8dpZ0BPC+YBdSHrS80iOLvbg@mail.gmail.com>
On 02/01, Linus Torvalds wrote:
>
> On Sun, Feb 1, 2015 at 11:43 AM, Oleg Nesterov <oleg@redhat.com> 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.
next prev parent reply other threads:[~2015-02-01 20:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 9:17 Linux 3.19-rc5 Linus Torvalds
2015-01-19 18:02 ` Bruno Prémont
2015-01-20 6:24 ` Linus Torvalds
2015-01-21 20:37 ` Bruno Prémont
2015-01-21 21:37 ` Bruno Prémont
2015-01-21 22:12 ` Davidlohr Bueso
2015-01-21 22:54 ` Peter Hurley
2015-01-30 1:22 ` Rafael J. Wysocki
2015-01-30 1:12 ` Linus Torvalds
2015-01-30 1:25 ` Linus Torvalds
2015-01-30 1:35 ` Linus Torvalds
2015-01-30 2:06 ` Rafael J. Wysocki
2015-01-30 15:47 ` Oleg Nesterov
2015-01-31 18:32 ` Linus Torvalds
2015-01-31 20:16 ` Peter Zijlstra
2015-01-31 21:54 ` Linus Torvalds
2015-02-02 13:19 ` Peter Zijlstra
2015-02-01 19:43 ` Oleg Nesterov
2015-02-01 20:09 ` Linus Torvalds
2015-02-01 20:19 ` Oleg Nesterov [this message]
2015-02-02 15:34 ` Peter Zijlstra
2015-01-31 9:16 ` Bruno Prémont
2015-01-31 9:48 ` Peter Zijlstra
2015-02-03 11:18 ` Ingo Molnar
2015-02-05 21:14 ` Bruno Prémont
2015-02-06 11:50 ` Peter Zijlstra
2015-02-06 16:02 ` Linus Torvalds
2015-02-06 16:39 ` Peter Zijlstra
2015-02-06 16:46 ` Linus Torvalds
2015-01-30 1:49 ` Rafael J. Wysocki
2015-02-02 9:48 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150201201915.GA31945@redhat.com \
--to=oleg@redhat.com \
--cc=bonbons@linux-vserver.org \
--cc=dave@stgolabs.net \
--cc=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.