linux-kernel - Re: [PATCH 1/2] panic: ratelimit panic messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 5 Jan 2011 09:00:24 -0500
From:	Don Zickus <dzickus@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	akpm@...ux-foundation.org, fweisbec@...il.com,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 1/2] panic:  ratelimit panic messages

On Wed, Jan 05, 2011 at 02:21:08PM +0100, Ingo Molnar wrote:
> 
> * Don Zickus <dzickus@...hat.com> wrote:
> 
> > Sometimes when things go bad, so much spew is coming on the console it is hard
> > to figure out what happened.  This patch allows you to ratelimit the panic
> > messages with the intent that the first panic message will provide the info
> > we need to figure out what happened.
> > 
> > Adds new kernel param 'panic_ratelimit=on/<integer in seconds>'
> > 
> > Signed-off-by: Don Zickus <dzickus@...hat.com>
> > ---
> >  Documentation/kernel-parameters.txt |    6 ++++++
> >  kernel/panic.c                      |   30 ++++++++++++++++++++++++++++++
> >  2 files changed, 36 insertions(+), 0 deletions(-)
> 
> Well, but it's not just panics that can occur repeatedly (in fact panics tend to 
> trigger once), but recursive/repeated oopses.
> 
> So if we try to do some sort of 'show first crash, rate-limit afterwards' thing (i'm 
> still not 100% sure about the wiseness of it) then we should cover all common 
> occurances of system panics/crashes.
> 
> btw., while printk-delay exists and can serve a similar purpose, it's pretty 
> cumbersome for panic ratelimit: it slows down bootups extremely, and it also slows 
> down regular, harmless printks.
> 
> So having some sort of rate-limit for emitting crash screens may make sense, while 
> also preserving the oops counter or at least some other notification that we 'lost' 
> messages.

Ok.  I guess I am feeling a little slow today.  So would moving this to
the kmsg_dump() function be the right place then?

Cheers,
Don

> 
> 	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/