linux.git/Documentation/oops-tracing.txt, branch master

docs-rst: create an user's manual book

2016-10-24T10:12:35+00:00

Place README, REPORTING-BUGS, SecurityBugs and kernel-parameters
on an user's manual book.

As we'll be numbering the user's manual, remove the manual
numbering from SecurityBugs.

Signed-off-by: Mauro Carvalho Chehab

Documentation/oops-tracing.txt: convert to ReST markup

2016-10-24T10:12:35+00:00

- Add a document title;
- use .. note:: markup;
- use quote blocks where needed;
- use monotonic fonts for config options and file names;
- adjust whitespaces and blank lines;
- replace _foo_ by **foo**;
- while here, remove whitespaces at the end of paragraph;
- add it to the user's book.

Signed-off-by: Mauro Carvalho Chehab

livepatch: kernel: add TAINT_LIVEPATCH

2014-12-22T14:40:48+00:00

This adds a new taint flag to indicate when the kernel or a kernel
module has been live patched.  This will provide a clean indication in
bug reports that live patching was used.

Additionally, if the crash occurs in a live patched function, the live
patch module will appear beside the patched function in the backtrace.

Signed-off-by: Seth Jennings 
Acked-by: Josh Poimboeuf 
Reviewed-by: Miroslav Benes 
Reviewed-by: Petr Mladek 
Reviewed-by: Masami Hiramatsu 
Signed-off-by: Jiri Kosina

panic: add TAINT_SOFTLOCKUP

2014-08-08T22:57:24+00:00

This taint flag will be set if the system has ever entered a softlockup
state.  Similar to TAINT_WARN it is useful to know whether or not the
system has been in a softlockup state when debugging.

[akpm@linux-foundation.org: apply the taint before calling panic()]
Signed-off-by: Josh Hunt 
Cc: Jason Baron 
Cc: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Use 'E' instead of 'X' for unsigned module taint flag.

2014-03-31T04:22:43+00:00

Takashi Iwai  says:
> The letter 'X' has been already used for SUSE kernels for very long
> time, to indicate the external supported modules.  Can the new flag be
> changed to another letter for avoiding conflict...?
> (BTW, we also use 'N' for "no support", too.)

Note: this code should be cleaned up, so we don't have such maps in
three places!

Signed-off-by: Rusty Russell

Fix: module signature vs tracepoints: add new TAINT_UNSIGNED_MODULE

2014-03-13T01:41:51+00:00

Users have reported being unable to trace non-signed modules loaded
within a kernel supporting module signature.

This is caused by tracepoint.c:tracepoint_module_coming() refusing to
take into account tracepoints sitting within force-loaded modules
(TAINT_FORCED_MODULE). The reason for this check, in the first place, is
that a force-loaded module may have a struct module incompatible with
the layout expected by the kernel, and can thus cause a kernel crash
upon forced load of that module on a kernel with CONFIG_TRACEPOINTS=y.

Tracepoints, however, specifically accept TAINT_OOT_MODULE and
TAINT_CRAP, since those modules do not lead to the "very likely system
crash" issue cited above for force-loaded modules.

With kernels having CONFIG_MODULE_SIG=y (signed modules), a non-signed
module is tainted re-using the TAINT_FORCED_MODULE taint flag.
Unfortunately, this means that Tracepoints treat that module as a
force-loaded module, and thus silently refuse to consider any tracepoint
within this module.

Since an unsigned module does not fit within the "very likely system
crash" category of tainting, add a new TAINT_UNSIGNED_MODULE taint flag
to specifically address this taint behavior, and accept those modules
within Tracepoints. We use the letter 'X' as a taint flag character for
a module being loaded that doesn't know how to sign its name (proposed
by Steven Rostedt).

Also add the missing 'O' entry to trace event show_module_flags() list
for the sake of completeness.

Signed-off-by: Mathieu Desnoyers 
Acked-by: Steven Rostedt 
NAKed-by: Ingo Molnar 
CC: Thomas Gleixner 
CC: David Howells 
CC: Greg Kroah-Hartman 
Signed-off-by: Rusty Russell

module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree

2011-11-06T21:24:42+00:00

Use of the GPL or a compatible licence doesn't necessarily make the code
any good.  We already consider staging modules to be suspect, and this
should also be true for out-of-tree modules which may receive very
little review.

Signed-off-by: Ben Hutchings 
Reviewed-by: Dave Jones 
Acked-by: Greg Kroah-Hartman 
Signed-off-by: Rusty Russell  (patched oops-tracing.txt)

panic: Add taint flag TAINT_FIRMWARE_WORKAROUND ('I')

2010-05-19T07:37:43+00:00

This taint flag will initially be used when warning about invalid ACPI
DMAR tables.

Signed-off-by: Ben Hutchings 
Signed-off-by: David Woodhouse

panic: Allow warnings to set different taint flags

2010-05-19T07:36:48+00:00

WARN() is used in some places to report firmware or hardware bugs that
are then worked-around.  These bugs do not affect the stability of the
kernel and should not set the flag for TAINT_WARN.  To allow for this,
add WARN_TAINT() and WARN_TAINT_ONCE() macros that take a taint number
as argument.

Architectures that implement warnings using trap instructions instead
of calls to warn_slowpath_*() now implement __WARN_TAINT(taint)
instead of __WARN().

Signed-off-by: Ben Hutchings 
Acked-by: Helge Deller 
Tested-by: Paul Mundt 
Signed-off-by: David Woodhouse

docs: Describe the 'C' taint flag in oops-tracing.txt

2009-11-09T08:40:56+00:00

If some of the flags are documented there, they all should be.

Signed-off-by: Nick Bowler 
Acked-by: Randy Dunlap 
Signed-off-by: Jiri Kosina