From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756268AbcA2OL3 (ORCPT <rfc822;w@1wt.eu>);
	Fri, 29 Jan 2016 09:11:29 -0500
Received: from www.linutronix.de ([62.245.132.108]:57442 "EHLO
	Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751671AbcA2OL2 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 29 Jan 2016 09:11:28 -0500
Date: Fri, 29 Jan 2016 15:10:18 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Dmitry Vyukov <dvyukov@google.com>
cc: Oleg Nesterov <oleg@redhat.com>, Andrew Morton <akpm@linux-foundation.org>,
        Richard Weinberger <richard@nod.at>,
        "Amanieu d'Antras" <amanieu@gmail.com>,
        Chris Metcalf <cmetcalf@ezchip.com>,
        Andy Lutomirski <luto@amacapital.net>,
        Davidlohr Bueso <dave@stgolabs.net>,
        Vladimir Davydov <vdavydov@parallels.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: WARNING in set_restore_sigmask
In-Reply-To: <CACT4Y+aN+WJS=TKHJEG0-ZctkBCnvEidvhPZXTV_PzGLMenn6w@mail.gmail.com>
Message-ID: <alpine.DEB.2.11.1601291505580.3886@nanos>
References: <CACT4Y+a+O5MXtZd5U-3t_7vQFhGaRCwMhrTB5OCcN5s=i4sTJg@mail.gmail.com> <alpine.DEB.2.11.1601291246340.3886@nanos> <CACT4Y+aiwqvjzhWgpYpSWSRmOCZUq9ui73q0tvPRHb5z8YqVGA@mail.gmail.com> <alpine.DEB.2.11.1601291450540.3886@nanos>
 <CACT4Y+aN+WJS=TKHJEG0-ZctkBCnvEidvhPZXTV_PzGLMenn6w@mail.gmail.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001,URIBL_BLOCKED=0.001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 29 Jan 2016, Dmitry Vyukov wrote:
> On Fri, Jan 29, 2016 at 2:57 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> I need something that will work without supervision. I need to use
> /proc/sys/kernel/ftrace_dump_on_oops instead of
> /proc/sys/kernel/traceoff_on_warning then, right?
> 
> Quite some time? Does it dump trace from boot? In my setup kernel can
> work up to an hour under super heavy parallel workload... Need to
> check how it will cope with it.

The time depends on the serial speed and the trace buffer size and the number
of cpus. Don't worry about the uptime. The buffer is a ringbuffer with limited
capacity, so the dump time is constant.

If you want that /proc/sys/kernel/ftrace_dump_on_oops spills out on warnings
as well, you need to enable

/proc/sys/kernel/traceoff_on_warning
/proc/sys/kernel/ftrace_dump_on_oops

and 

/proc/sys/kernel/panic_on_warn

because we do not dump on warnings.

Thanks,

	tglx