archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <>,
	Kees Cook <>
Cc: Linux Kernel Mailing List <>,
	Alexander Popov <>,
	Dave Hansen <>,
	"Ingo Molnar" <>,
	Masahiro Yamada <>,
	Thomas Gleixner <>,
	Tycho Andersen <>,
	"Mark Rutland" <>,
	Laura Abbott <>,
	"Will Deacon" <>
Subject: RE: [GIT PULL] gcc-plugin updates for v4.19-rc1
Date: Thu, 16 Aug 2018 09:51:41 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

From: Linus Torvalds
> Sent: 15 August 2018 21:19
> But if people run things on real machines, then BUG() is absolutely
> the last thing you EVER want to do for "debugging".

I'm not sure you want it on a live system either.
Live systems are where the 'hard' bugs show up.

I've just spent a couple of days pulling my hair out trying to work
out how to debug a customer system that was locking up solid when
running some new (and not completely testable by us) kernel code.

At 4am I suddenly realised that the distribution they are using
might be enabling 'panic_on_oops' by default.
Turning that off showed what was going wrong.

It wouldn't be as bad if Linux implemented 'dump to swap'.

For 'errors' that aren't completely fatal the system could
'fast shutdown' a lot of processes (maybe just refuse to schedule
them) while leaving enough running for fault diagnosis.
I'm not sure how you'd decide what to allow to run though.


Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

      parent reply	other threads:[~2018-08-16  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 21:43 [GIT PULL] gcc-plugin updates for v4.19-rc1 Kees Cook
2018-08-15 16:41 ` Linus Torvalds
2018-08-15 18:35   ` Kees Cook
2018-08-15 19:04     ` Linus Torvalds
2018-08-15 19:43       ` Alexander Popov
2018-08-15 19:45       ` Kees Cook
2018-08-15 20:18         ` Linus Torvalds
2018-08-15 20:56           ` Kees Cook
2018-08-15 21:18             ` Alexander Popov
2018-08-15 21:33               ` Linus Torvalds
2018-08-16 22:18             ` Alexander Popov
2018-08-16  9:51           ` David Laight [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).