All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	stable@vger.kernel.org, rabinv@axis.com,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: Request for inclusion of fb90a6e93c0684 ("sched/debug: Don't dump sched debug info in SysRq-W")
Date: Wed, 15 Feb 2017 09:07:42 -0800	[thread overview]
Message-ID: <20170215170742.GA3651@kroah.com> (raw)
In-Reply-To: <193a5ad1-b128-4809-ffeb-16c5a6889efa@gmail.com>

On Wed, Feb 15, 2017 at 11:17:34AM +0200, Nikolay Borisov wrote:
> On 15.02.2017 11:13, Peter Zijlstra wrote:
> > On Wed, Feb 15, 2017 at 11:09:14AM +0200, Nikolay Borisov wrote:
> >> Hello,
> >>
> >> I'd like to ask for the patch in the subject to be included in stable
> >> kernels. Without it if one wants to see only the blocked stats this
> >> becomes impossible since the information dumped by sched_debug is so
> >> much that it overflows the kmsg buffer and information about blocked
> >> stats is overwritten. This is especially a problem in distro kernels
> >> which are based on 4.4 and have enabled CONFIG_SCHED_DEBUG - e.g. ubuntu.
> > 
> > Who cares about the kmsg buffer? Also, just make it bigger or disable
> > SCHED_DEBUG, as the name implies it _is_ a debug feature after all.
> 
> but what if you want to use your distro's kernel and deal with custom
> recompiles.

That doesn't make sense, if your distro wants this information, it gets
to pick what it wants.

> The kernel ought to come with sensible defaults.

You can turn it off if you have problems with it, I don't see this
meeting the stable kernel rules.

thanks,

greg k-h

      reply	other threads:[~2017-02-15 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  9:09 Request for inclusion of fb90a6e93c0684 ("sched/debug: Don't dump sched debug info in SysRq-W") Nikolay Borisov
2017-02-15  9:12 ` Ingo Molnar
2017-02-15  9:13 ` Peter Zijlstra
2017-02-15  9:17   ` Nikolay Borisov
2017-02-15 17:07     ` Greg KH [this message]

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=20170215170742.GA3651@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=mingo@kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rabinv@axis.com \
    --cc=stable@vger.kernel.org \
    /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.