All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	linux-sh@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ben Segall <bsegall@google.com>, Guo Ren <guoren@kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Paul Burton <paulburton@kernel.org>,
	Dmitry Safonov <dima@arista.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Mel Gorman <mgorman@suse.de>, Jiri Slaby <jslaby@suse.com>,
	Matt Turner <mattst88@gmail.com>,
	uclinux-h8-devel@lists.sourceforge.jp,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-um@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Richard Henderson <rth@twiddle.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	James Hogan <jhogan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Vincent Chen <deanbo422@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-hexagon@vger.kernel.org, Helge Deller <deller@gmx.de>,
	linux-xtensa@linux-xtensa.org, Vasily Gorbik <gor@linux.ibm.com>,
	Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
	linux-m68k@lists.linux-m68k.org,
	Stafford Horne <shorne@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Chris Zankel <chris@zankel.net>, Tony Luck <tony.luck@intel.com>,
	Douglas Anderson <dianders@chromium.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Will Deacon <will@kernel.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Brian Cain <bcain@codeaurora.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-snps-arc@lists.infradead.org,
	Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@alien8.de>,
	Jeff Dike <jdike@addtoit.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greentime Hu <green.hu@gmail.com>, Guan Xuetao <gxt@pku.edu.cn>,
	linux-parisc@vger.kernel.org, linux-alpha@vger.kernel.org,
	Ley Foon Tan <lftan@altera.com>,
	"David S. Miller" <davem@davemloft.net>,
	Rich Felker <dalias@libc.org>, Petr Mladek <pmladek@suse.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Jonas Bonn <jonas@southpole.se>,
	Richard Weinberger <richard@nod.at>,
	x86@kernel.org, clang-built-linux@googlegroups.com,
	Ingo Molnar <mingo@redhat.com>, Mark Salter <msalter@redhat.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	openrisc@lists.librecores.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Michal Simek <monstr@monstr.eu>,
	Vineet Gupta <vgupta@synopsys.com>,
	linux-mips@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	nios2-dev@lists.rocketboards.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	linux-sh@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ben Segall <bsegall@google.com>, Guo Ren <guoren@kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Paul Burton <paulburton@kernel.org>,
	Dmitry Safonov <dima@arista.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Mel Gorman <mgorman@suse.de>, Jiri Slaby <jslaby@suse.com>,
	Matt Turner <mattst88@gmail.com>,
	uclinux-h8-devel@lists.sourceforge.jp,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-um@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Richard Henderson <rth@twiddle.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	James Hogan <jhogan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Vincent Chen <deanbo422@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-hexagon@vger.kernel.org, Helge Deller <deller@gmx.de>,
	linux-xtensa@linux-xtensa.org, Vasily Gorbik <gor@linux.ibm.com>,
	Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
	linux-m68k@lists.linux-m68k.org,
	Stafford Horne <shorne@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Chris Zankel <chris@zankel.net>, Tony Luck <tony.luck@intel.com>,
	Douglas Anderson <dianders@chromium.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Will Deacon <will@kernel.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Brian Cain <bcain@codeaurora.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-snps-arc@lists.infradead.org,
	Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@alien8.de>,
	Jeff Dike <jdike@addtoit.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greentime Hu <green.hu@gmail.com>, Guan Xuetao <gxt@pku.edu.cn>,
	linux-parisc@vger.kernel.org, linux-alpha@vger.kernel.org,
	Ley Foon Tan <lftan@altera.com>,
	"David S. Miller" <davem@davemloft.net>,
	Rich Felker <dalias@libc.org>, Petr Mladek <pmladek@suse.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Jonas Bonn <jonas@southpole.se>,
	Richard Weinberger <richard@nod.at>,
	x86@kernel.org, clang-built-linux@googlegroups.com,
	Ingo Molnar <mingo@redhat.com>, Mark Salter <msalter@redhat.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	openrisc@lists.librecores.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Michal Simek <monstr@monstr.eu>,
	Vineet Gupta <vgupta@synopsys.com>,
	linux-mips@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	nios2-dev@lists.rocketboards.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	linux-sh@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ben Segall <bsegall@google.com>, Guo Ren <guoren@kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Paul Burton <paulburton@kernel.org>,
	Dmitry Safonov <dima@arista.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Mel Gorman <mgorman@suse.de>, Jiri Slaby <jslaby@suse.com>,
	Matt Turner <mattst88@gmail.com>,
	uclinux-h8-devel@lists.sourceforge.jp,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-um@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Richard Henderson <rth@twiddle.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	James Hogan <jhogan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Vincent Chen <deanbo422@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-hexagon@vger.kernel.org, Helge Deller <deller@gmx.de>,
	linux-xtensa@linux-xtensa.org, Vasily Gorbik <gor@linux.ibm.com>,
	Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
	linux-m68k@lists.linux-m68k.org,
	Stafford Horne <shorne@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Chris Zankel <chris@zankel.net>, Tony Luck <tony.luck@intel.com>,
	Douglas Anderson <dianders@chromium.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Will Deacon <will@kernel.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Brian Cain <bcain@codeaurora.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-snps-arc@lists.infradead.org,
	Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@alien8.de>,
	Jeff Dike <jdike@addtoit.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greentime Hu <green.hu@gmail.com>, Guan Xuetao <gxt@pku.edu.cn>,
	linux-parisc@vger.kernel.org, linux-alpha@vger.kernel.org,
	Ley Foon Tan <lftan@altera.com>,
	"David S. Miller" <davem@davemloft.net>,
	Rich Felker <dalias@libc.org>, Petr Mladek <pmladek@suse.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Jonas Bonn <jonas@southpole.se>,
	Richard Weinberger <richard@nod.at>,
	x86@kernel.org, clang-built-linux@googlegroups.com,
	Ingo Molnar <mingo@redhat.com>, Mark Salter <msalter@redhat.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	openrisc@lists.librecores.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Michal Simek <monstr@monstr.eu>,
	Vineet Gupta <vgupta@synopsys.com>,
	linux-mips@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	nios2-dev@lists.rocketboards.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	linux-sh@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ben Segall <bsegall@google.com>, Guo Ren <guoren@kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Paul Burton <paulburton@kernel.org>,
	Dmitry Safonov <dima@arista.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Mel Gorman <mgorman@suse.de>, Jiri Slaby <jslaby@suse.com>,
	Matt Turner <mattst88@gmail.com>,
	uclinux-h8-devel@lists.sourceforge.jp,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-um@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Richard Henderson <rth@twiddle.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ia64@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	James Hogan <jhogan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Vincent Chen <deanbo422@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-hexagon@vger.kernel.org, Helge Deller <deller@gmx.de>,
	linux-xtensa@linux-xtensa.org, Vasily Gorbik <gor@linux.ibm.com>,
	Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
	linux-m68k@lists.linux-m68k.org,
	Stafford Horne <shorne@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Chris Zankel <chris@zankel.net>, Tony Luck <tony.luck@intel.com>,
	Douglas Anderson <dianders@chromium.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Will Deacon <will@kernel.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Brian Cain <bcain@codeaurora.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-snps-arc@lists.infradead.org,
	Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@alien8.de>,
	Jeff Dike <jdike@addtoit.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greentime Hu <green.hu@gmail.com>, Guan Xuetao <gxt@pku.edu.cn>,
	linux-parisc@vger.kernel.org, linux-alpha@vger.kernel.org,
	Ley Foon Tan <lftan@altera.com>,
	"David S. Miller" <davem@davemloft.net>,
	Rich Felker <dalias@libc.org>, Petr Mladek <pmladek@suse.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Jonas Bonn <jonas@southpole.se>,
	Richard Weinberger <richard@nod.at>,
	x86@kernel.org, clang-built-linux@googlegroups.com,
	Ingo Molnar <mingo@redhat.com>, Mark Salter <msalter@redhat.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	openrisc@lists.librecores.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Michal Simek <monstr@monstr.eu>,
	Vineet Gupta <vgupta@synopsys.com>,
	linux-mips@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	nios2-dev@lists.rocketboards.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	linux-sh@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ben Segall <bsegall@google.com>, Guo Ren <guoren@kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Paul Burton <paulburton@kernel.org>,
	Dmitry Safonov <dima@arista.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Mel Gorman <mgorman@suse.de>, Jiri Slaby <jslaby@suse.com>,
	Matt Turner <mattst88@gmail.com>,
	uclinux-h8-devel@lists.sourceforge.jp,
	Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-um@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Richard Henderson <rth@twiddle.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kerne
Subject: Re: [PATCH 00/50] Add log level to show_stack()
Date: Wed, 6 Nov 2019 23:25:13 +0000	[thread overview]
Message-ID: <20191106232512.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191106203440.GH3079@worktop.programming.kicks-ass.net>

On Wed, Nov 06, 2019 at 09:34:40PM +0100, Peter Zijlstra wrote:
> I suppose I'm surprised there are backtraces that are not important.
> Either badness happened and it needs printing, or the user asked for it
> and it needs printing.

Or utterly meaningless.

> Perhaps we should be removing backtraces if they're not important
> instead of allowing to print them as lower loglevels?

Definitely!  WARN_ON() is well overused - and as is typical, used
without much thought.  Bound to happen after Linus got shirty about
BUG_ON() being over used.  Everyone just grabbed the next nearest thing
to assert().

As a kind of example, I've recently come across one WARN_ON() in a
driver subsystem (that shall remain nameless at the moment) which very
likely has multiple different devices on a platform.  The WARN_ON()
triggers as a result of a problem with the hardware, but because it's a
WARN_ON(), you've no idea which device has a problem.  The backtrace is
mostly meaningless.  So you know that a problem has occurred, but the
kernel prints *useless* backtrace to let you know, and totally omits
the *useful* information.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

  reply	other threads:[~2019-11-06 23:28 UTC|newest]

Thread overview: 323+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  3:04 [PATCH 00/50] Add log level to show_stack() Dmitry Safonov
2019-11-06  3:04 ` Dmitry Safonov
2019-11-06  3:04 ` Dmitry Safonov
2019-11-06  3:04 ` [OpenRISC] " Dmitry Safonov
2019-11-06  3:04 ` Dmitry Safonov
2019-11-06  3:04 ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 01/50] kallsyms/printk: Add loglvl to print_ip_sym() Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  4:38   ` Sergey Senozhatsky
2019-11-06  4:38     ` Sergey Senozhatsky
2019-11-06 16:39     ` Dmitry Safonov
2019-11-06 16:39       ` Dmitry Safonov
2019-11-13 15:49   ` Steven Rostedt
2019-11-13 15:49     ` Steven Rostedt
2019-11-06  3:04 ` [PATCH 02/50] alpha: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:04 ` [PATCH 03/50] arc: " Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 04/50] arm/asm: Add loglvl to c_backtrace() Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 05/50] arm: Add loglvl to unwind_backtrace() Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  9:12   ` Russell King - ARM Linux admin
2019-11-06  9:12     ` Russell King - ARM Linux admin
2019-11-06 16:32     ` Dmitry Safonov
2019-11-06 16:32       ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 06/50] arm: Add loglvl to dump_backtrace() Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 07/50] arm: Wire up dump_backtrace_{entry,stm} Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  3:04 ` [PATCH 08/50] arm: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:04   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 09/50] arm64: Add loglvl to dump_backtrace() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06 13:25   ` Will Deacon
2019-11-06 13:25     ` Will Deacon
2019-11-06 16:00     ` Dmitry Safonov
2019-11-06 16:00       ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 10/50] arm64: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 11/50] c6x: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 12/50] csky: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 13/50] h8300: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 14/50] hexagon: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 15/50] ia64: Pass log level as arg into ia64_do_show_stack() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 16/50] ia64: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 17/50] m68k: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 18/50] microblaze: Add loglvl to microblaze_unwind_inner() Dmitry Safonov
2019-11-07  8:59   ` Michal Simek
2019-11-08  7:52   ` kbuild test robot
2019-11-08  7:52     ` kbuild test robot
2019-11-06  3:05 ` [PATCH 19/50] microblaze: Add loglvl to microblaze_unwind() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 20/50] microblaze: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 21/50] mips: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 22/50] nds32: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 23/50] nios2: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 24/50] openrisc: " Dmitry Safonov
2019-11-06  3:05   ` [OpenRISC] " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 25/50] parisc: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 26/50] powerpc: " Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  9:52   ` Michael Ellerman
2019-11-06  9:52     ` Michael Ellerman
2019-11-06 16:01     ` Dmitry Safonov
2019-11-06 16:01       ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 27/50] riscv: " Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 28/50] s390: " Dmitry Safonov
2019-11-06  3:05 ` [PATCH 29/50] sh: Add loglvl to dump_mem() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 30/50] sh: Remove needless printk() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 31/50] sh: Add loglvl to printk_address() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 32/50] sh: Add loglvl to show_trace() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 33/50] sh: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 34/50] sparc: " Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:33   ` David Miller
2019-11-06  3:33     ` David Miller
2019-11-06 16:02     ` Dmitry Safonov
2019-11-06 16:02       ` Dmitry Safonov
2019-11-08  7:08   ` kbuild test robot
2019-11-08  7:08     ` kbuild test robot
2019-11-08  7:08     ` kbuild test robot
2019-11-06  3:05 ` [PATCH 35/50] um/sysrq: Remove needless variable sp Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 36/50] um: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05   ` Dmitry Safonov
2019-11-06  3:05 ` [PATCH 37/50] unicore32: Remove unused pmode argument in c_backtrace() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 38/50] unicore32: Add loglvl to c_backtrace() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 39/50] unicore32: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 40/50] x86: Add missing const qualifiers for log_lvl Dmitry Safonov
2019-11-06  3:05 ` [PATCH 41/50] x86: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 42/50] xtensa: Add loglvl to show_trace() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 43/50] xtensa: Add show_stack_loglvl() Dmitry Safonov
2019-11-06  4:13   ` Max Filippov
2019-11-06  8:15     ` Petr Mladek
2019-11-06 16:06       ` Dmitry Safonov
2019-11-06 16:44       ` Max Filippov
2019-11-06  3:05 ` [PATCH 44/50] sysrq: Use show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 45/50] x86/amd_gart: Print stacktrace for a leak with KERN_ERR Dmitry Safonov
2019-11-06  3:05 ` [PATCH 46/50] power: Use show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 47/50] kdb: Don't play with console_loglevel Dmitry Safonov
2019-11-06  3:05 ` [PATCH 48/50] sched: Print stack trace with KERN_INFO Dmitry Safonov
2019-11-06  3:05 ` [PATCH 49/50] kernel: Use show_stack_loglvl() Dmitry Safonov
2019-11-06  3:05 ` [PATCH 50/50] kernel: Rename show_stack_loglvl() => show_stack() Dmitry Safonov
2019-11-08 10:08   ` kbuild test robot
2019-11-08 10:08     ` kbuild test robot
2019-11-06  8:35 ` [PATCH 00/50] Add log level to show_stack() Petr Mladek
2019-11-06  8:35   ` Petr Mladek
2019-11-06  8:35   ` Petr Mladek
2019-11-06  8:35   ` [OpenRISC] " Petr Mladek
2019-11-06  8:35   ` Petr Mladek
2019-11-06  8:35   ` Petr Mladek
2019-11-06 16:12   ` Dmitry Safonov
2019-11-06 16:12     ` Dmitry Safonov
2019-11-06 16:12     ` Dmitry Safonov
2019-11-06 16:12     ` [OpenRISC] " Dmitry Safonov
2019-11-06 16:12     ` Dmitry Safonov
2019-11-06 16:12     ` Dmitry Safonov
2019-11-08 10:37   ` Sergey Senozhatsky
2019-11-08 10:37     ` Sergey Senozhatsky
2019-11-08 10:37     ` Sergey Senozhatsky
2019-11-08 10:37     ` [OpenRISC] " Sergey Senozhatsky
2019-11-08 10:37     ` Sergey Senozhatsky
2019-11-08 10:37     ` Sergey Senozhatsky
2019-11-08 13:04     ` Petr Mladek
2019-11-08 13:04       ` Petr Mladek
2019-11-08 13:04       ` Petr Mladek
2019-11-08 13:04       ` [OpenRISC] " Petr Mladek
2019-11-08 13:04       ` Petr Mladek
2019-11-08 13:04       ` Petr Mladek
2019-11-11  1:23       ` Sergey Senozhatsky
2019-11-11  1:23         ` Sergey Senozhatsky
2019-11-11  1:23         ` Sergey Senozhatsky
2019-11-11  1:23         ` [OpenRISC] " Sergey Senozhatsky
2019-11-11  1:23         ` Sergey Senozhatsky
2019-11-11  1:23         ` Sergey Senozhatsky
2019-11-11  9:12         ` Petr Mladek
2019-11-11  9:12           ` Petr Mladek
2019-11-11  9:12           ` Petr Mladek
2019-11-11  9:12           ` [OpenRISC] " Petr Mladek
2019-11-11  9:12           ` Petr Mladek
2019-11-11  9:12           ` Petr Mladek
2019-11-12  4:44           ` Sergey Senozhatsky
2019-11-12  4:44             ` Sergey Senozhatsky
2019-11-12  4:44             ` Sergey Senozhatsky
2019-11-12  4:44             ` [OpenRISC] " Sergey Senozhatsky
2019-11-12  4:44             ` Sergey Senozhatsky
2019-11-12  4:44             ` Sergey Senozhatsky
2019-11-12  4:57             ` Sergey Senozhatsky
2019-11-12  4:57               ` Sergey Senozhatsky
2019-11-12  4:57               ` Sergey Senozhatsky
2019-11-12  4:57               ` [OpenRISC] " Sergey Senozhatsky
2019-11-12  4:57               ` Sergey Senozhatsky
2019-11-12  4:57               ` Sergey Senozhatsky
2019-11-12  8:35               ` Petr Mladek
2019-11-12  8:35                 ` Petr Mladek
2019-11-12  8:35                 ` Petr Mladek
2019-11-12  8:35                 ` [OpenRISC] " Petr Mladek
2019-11-12  8:35                 ` Petr Mladek
2019-11-12  8:35                 ` Petr Mladek
2019-11-12 10:12                 ` Sergey Senozhatsky
2019-11-12 10:12                   ` Sergey Senozhatsky
2019-11-12 10:12                   ` Sergey Senozhatsky
2019-11-12 10:12                   ` [OpenRISC] " Sergey Senozhatsky
2019-11-12 10:12                   ` Sergey Senozhatsky
2019-11-12 10:12                   ` Sergey Senozhatsky
2019-11-13  1:23                   ` Sergey Senozhatsky
2019-11-13  1:23                     ` Sergey Senozhatsky
2019-11-13  1:23                     ` Sergey Senozhatsky
2019-11-13  1:23                     ` [OpenRISC] " Sergey Senozhatsky
2019-11-13  1:23                     ` Sergey Senozhatsky
2019-11-13  1:23                     ` Sergey Senozhatsky
2019-11-13  2:25                     ` Dmitry Safonov
2019-11-13  2:25                       ` Dmitry Safonov
2019-11-13  2:25                       ` Dmitry Safonov
2019-11-13  2:25                       ` [OpenRISC] " Dmitry Safonov
2019-11-13  2:25                       ` Dmitry Safonov
2019-11-13  2:25                       ` Dmitry Safonov
2019-11-13  6:33                       ` Sergey Senozhatsky
2019-11-13  6:33                         ` Sergey Senozhatsky
2019-11-13  6:33                         ` Sergey Senozhatsky
2019-11-13  6:33                         ` [OpenRISC] " Sergey Senozhatsky
2019-11-13  6:33                         ` Sergey Senozhatsky
2019-11-13  6:33                         ` Sergey Senozhatsky
2019-11-13  8:47                         ` Petr Mladek
2019-11-13  8:47                           ` Petr Mladek
2019-11-13  8:47                           ` Petr Mladek
2019-11-13  8:47                           ` [OpenRISC] " Petr Mladek
2019-11-13  8:47                           ` Petr Mladek
2019-11-13  8:47                           ` Petr Mladek
2019-11-13 16:24                           ` Steven Rostedt
2019-11-13 16:24                             ` Steven Rostedt
2019-11-13 16:24                             ` Steven Rostedt
2019-11-13 16:24                             ` [OpenRISC] " Steven Rostedt
2019-11-13 16:24                             ` Steven Rostedt
2019-11-13 16:24                             ` Steven Rostedt
2019-11-13 16:40                         ` Dmitry Safonov
2019-11-13 16:40                           ` Dmitry Safonov
2019-11-13 16:40                           ` Dmitry Safonov
2019-11-13 16:40                           ` [OpenRISC] " Dmitry Safonov
2019-11-13 16:40                           ` Dmitry Safonov
2019-11-13 16:40                           ` Dmitry Safonov
2019-11-15  0:50                           ` Sergey Senozhatsky
2019-11-15  0:50                             ` Sergey Senozhatsky
2019-11-15  0:50                             ` Sergey Senozhatsky
2019-11-15  0:50                             ` [OpenRISC] " Sergey Senozhatsky
2019-11-15  0:50                             ` Sergey Senozhatsky
2019-11-15  0:50                             ` Sergey Senozhatsky
2019-11-13 15:32             ` Steven Rostedt
2019-11-13 15:32               ` Steven Rostedt
2019-11-13 15:32               ` Steven Rostedt
2019-11-13 15:32               ` [OpenRISC] " Steven Rostedt
2019-11-13 15:32               ` Steven Rostedt
2019-11-13 15:32               ` Steven Rostedt
2019-11-11 19:47         ` Dmitry Safonov
2019-11-11 19:47           ` Dmitry Safonov
2019-11-11 19:47           ` Dmitry Safonov
2019-11-11 19:47           ` [OpenRISC] " Dmitry Safonov
2019-11-11 19:47           ` Dmitry Safonov
2019-11-11 19:47           ` Dmitry Safonov
2019-11-12  2:17           ` Sergey Senozhatsky
2019-11-12  2:17             ` Sergey Senozhatsky
2019-11-12  2:17             ` Sergey Senozhatsky
2019-11-12  2:17             ` [OpenRISC] " Sergey Senozhatsky
2019-11-12  2:17             ` Sergey Senozhatsky
2019-11-12  2:17             ` Sergey Senozhatsky
2019-11-12  2:40             ` Dmitry Safonov
2019-11-12  2:40               ` Dmitry Safonov
2019-11-12  2:40               ` Dmitry Safonov
2019-11-12  2:40               ` [OpenRISC] " Dmitry Safonov
2019-11-12  2:40               ` Dmitry Safonov
2019-11-12  2:40               ` Dmitry Safonov
2019-11-12  4:25               ` Sergey Senozhatsky
2019-11-12  4:25                 ` Sergey Senozhatsky
2019-11-12  4:25                 ` Sergey Senozhatsky
2019-11-12  4:25                 ` [OpenRISC] " Sergey Senozhatsky
2019-11-12  4:25                 ` Sergey Senozhatsky
2019-11-12  4:25                 ` Sergey Senozhatsky
2019-11-13  2:41                 ` Dmitry Safonov
2019-11-13  2:41                   ` Dmitry Safonov
2019-11-13  2:41                   ` Dmitry Safonov
2019-11-13  2:41                   ` [OpenRISC] " Dmitry Safonov
2019-11-13  2:41                   ` Dmitry Safonov
2019-11-13  2:41                   ` Dmitry Safonov
2019-11-13  2:51                   ` Sergey Senozhatsky
2019-11-13  2:51                     ` Sergey Senozhatsky
2019-11-13  2:51                     ` Sergey Senozhatsky
2019-11-13  2:51                     ` [OpenRISC] " Sergey Senozhatsky
2019-11-13  2:51                     ` Sergey Senozhatsky
2019-11-13  2:51                     ` Sergey Senozhatsky
2019-11-13 15:39             ` Steven Rostedt
2019-11-13 15:39               ` Steven Rostedt
2019-11-13 15:39               ` Steven Rostedt
2019-11-13 15:39               ` [OpenRISC] " Steven Rostedt
2019-11-13 15:39               ` Steven Rostedt
2019-11-13 15:39               ` Steven Rostedt
2019-11-15  3:36               ` Sergey Senozhatsky
2019-11-15  3:36                 ` Sergey Senozhatsky
2019-11-15  3:36                 ` Sergey Senozhatsky
2019-11-15  3:36                 ` [OpenRISC] " Sergey Senozhatsky
2019-11-15  3:36                 ` Sergey Senozhatsky
2019-11-15  3:36                 ` Sergey Senozhatsky
2019-11-06  9:20 ` Peter Zijlstra
2019-11-06  9:20   ` Peter Zijlstra
2019-11-06  9:20   ` Peter Zijlstra
2019-11-06  9:20   ` [OpenRISC] " Peter Zijlstra
2019-11-06  9:20   ` Peter Zijlstra
2019-11-06  9:20   ` Peter Zijlstra
2019-11-06 16:27   ` Dmitry Safonov
2019-11-06 16:27     ` Dmitry Safonov
2019-11-06 16:27     ` Dmitry Safonov
2019-11-06 16:27     ` [OpenRISC] " Dmitry Safonov
2019-11-06 16:27     ` Dmitry Safonov
2019-11-06 16:27     ` Dmitry Safonov
2019-11-06 20:34     ` Peter Zijlstra
2019-11-06 20:34       ` Peter Zijlstra
2019-11-06 20:34       ` Peter Zijlstra
2019-11-06 20:34       ` [OpenRISC] " Peter Zijlstra
2019-11-06 20:34       ` Peter Zijlstra
2019-11-06 20:34       ` Peter Zijlstra
2019-11-06 23:25       ` Russell King - ARM Linux admin [this message]
2019-11-06 23:25         ` Russell King - ARM Linux admin
2019-11-06 23:25         ` Russell King - ARM Linux admin
2019-11-06 23:25         ` [OpenRISC] " Russell King - ARM Linux admin
2019-11-06 23:25         ` Russell King - ARM Linux admin
2019-11-06 23:25         ` Russell King - ARM Linux admin
2019-11-07  7:27         ` Geert Uytterhoeven
2019-11-13 15:44         ` Steven Rostedt
2019-11-13 15:44           ` Steven Rostedt
2019-11-13 15:44           ` Steven Rostedt
2019-11-13 15:44           ` [OpenRISC] " Steven Rostedt
2019-11-13 15:44           ` Steven Rostedt
2019-11-13 15:44           ` Steven Rostedt
2019-11-08 16:28       ` Dmitry Safonov
2019-11-08 16:28         ` Dmitry Safonov
2019-11-08 16:28         ` Dmitry Safonov
2019-11-08 16:28         ` [OpenRISC] " Dmitry Safonov
2019-11-08 16:28         ` Dmitry Safonov
2019-11-08 16:28         ` Dmitry Safonov
2019-11-08 17:30         ` Russell King - ARM Linux admin
2019-11-08 17:30           ` Russell King - ARM Linux admin
2019-11-08 17:30           ` Russell King - ARM Linux admin
2019-11-08 17:30           ` [OpenRISC] " Russell King - ARM Linux admin
2019-11-08 17:30           ` Russell King - ARM Linux admin
2019-11-08 17:30           ` Russell King - ARM Linux admin
2019-11-08 21:08           ` Dmitry Safonov
2019-11-08 21:08             ` Dmitry Safonov
2019-11-08 21:08             ` Dmitry Safonov
2019-11-08 21:08             ` [OpenRISC] " Dmitry Safonov
2019-11-08 21:08             ` Dmitry Safonov
2019-11-08 21:08             ` Dmitry Safonov
2019-11-13 15:41       ` Steven Rostedt
2019-11-13 15:41         ` Steven Rostedt
2019-11-13 15:41         ` Steven Rostedt
2019-11-13 15:41         ` [OpenRISC] " Steven Rostedt
2019-11-13 15:41         ` Steven Rostedt
2019-11-13 15:41         ` Steven Rostedt

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=20191106232512.GU25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=0x7f454c46@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bcain@codeaurora.org \
    --cc=benh@kernel.crashing.org \
    --cc=borntraeger@de.ibm.com \
    --cc=bp@alien8.de \
    --cc=bsegall@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=chris@zankel.net \
    --cc=clang-built-linux@googlegroups.com \
    --cc=dalias@libc.org \
    --cc=daniel.thompson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=deanbo422@gmail.com \
    --cc=deller@gmx.de \
    --cc=dianders@chromium.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=dima@arista.com \
    --cc=fenghua.yu@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=gor@linux.ibm.com \
    --cc=green.hu@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guoren@kernel.org \
    --cc=gxt@pku.edu.cn \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jacquiot.aurelien@gmail.com \
    --cc=jason.wessel@windriver.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=jhogan@kernel.org \
    --cc=jonas@southpole.se \
    --cc=jslaby@suse.com \
    --cc=juri.lelli@redhat.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=lftan@altera.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-um@lists.infradead.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mattst88@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=monstr@monstr.eu \
    --cc=mpe@ellerman.id.au \
    --cc=msalter@redhat.com \
    --cc=nios2-dev@lists.rocketboards.org \
    --cc=openrisc@lists.librecores.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulburton@kernel.org \
    --cc=paulus@samba.org \
    --cc=pavel@ucw.cz \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=ralf@linux-mips.org \
    --cc=richard@nod.at \
    --cc=rjw@rjwysocki.net \
    --cc=rostedt@goodmis.org \
    --cc=rth@twiddle.net \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=shorne@gmail.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=uclinux-h8-devel@lists.sourceforge.jp \
    --cc=vgupta@synopsys.com \
    --cc=vincent.guittot@linaro.org \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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.