linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Kees Cook <keescook@chromium.org>,
	"Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, mcgrof@kernel.org, yzaikin@google.com,
	tglx@linutronix.de, kernel@gpiccoli.net
Subject: Re: [PATCH] kernel/hung_task.c: Introduce sysctl to print all traces when a hung task is detected
Date: Sat, 14 Mar 2020 13:27:13 +0900	[thread overview]
Message-ID: <c4b05b32-216a-e130-259f-0d9506ff9244@i-love.sakura.ne.jp> (raw)
In-Reply-To: <202003132011.8143A71FE@keescook>

On 2020/03/14 12:12, Kees Cook wrote:
> On Fri, Mar 13, 2020 at 02:23:37PM -0300, Guilherme G. Piccoli wrote:
>> Kees / Testsuo, are you OK with this patch once I resend with the
>> suggestions you gave me?
> 
> I think so, yes. Send a v2 (to akpm with us in CC).
> 
>> Is there anybody else I should loop in the patch that should take a
>> look? Never sent sysctl stuff before, sorry if I forgot somebody heheh
> 
> akpm usually takes these kinds of things.
> 

Well, maybe sysctl_hung_task_all_cpu_backtrace = 1 by default is better for
compatibility? Please CC or BCC kernel-testing people so that they can add
hung_task_all_cpu_backtrace=1 kernel command line parameter to their testing
environments if sysctl_hung_task_all_cpu_backtrace = 0 by default.

  reply	other threads:[~2020-03-15  2:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 15:56 [PATCH] kernel/hung_task.c: Introduce sysctl to print all traces when a hung task is detected Guilherme G. Piccoli
2020-03-10 16:05 ` Kees Cook
2020-03-13 17:23 ` Guilherme G. Piccoli
2020-03-14  3:12   ` Kees Cook
2020-03-14  4:27     ` Tetsuo Handa [this message]
2020-03-16 14:01       ` Guilherme G. Piccoli

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=c4b05b32-216a-e130-259f-0d9506ff9244@i-love.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=gpiccoli@canonical.com \
    --cc=keescook@chromium.org \
    --cc=kernel@gpiccoli.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yzaikin@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).