LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Randy Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] Document kernel taint flags properly
Date: Sat, 18 Oct 2008 03:51:11 -0500 [thread overview]
Message-ID: <cfd18e0f0810180151v232f623pdbf0f12cad6532d6@mail.gmail.com> (raw)
In-Reply-To: <20081017225515.GA14133@kroah.com>
Greg,
Small corrections below.
On Fri, Oct 17, 2008 at 5:55 PM, Greg KH <greg@kroah.com> wrote:
> From: Greg Kroah-Hartman <gregkh@suse.de>
>
> This fills in the documentation for all of the current kernel taint
> flags, and fixes the number for TAINT_CRAP, which was incorrectly
> described.
>
> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
> Cc: Randy Dunlap <rdunlap@xenotime.net>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
> Documentation/sysctl/kernel.txt | 24 +++++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
>
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -363,11 +363,21 @@ tainted:
> Non-zero if the kernel has been tainted. Numeric values, which
> can be ORed together:
>
> - 1 - A module with a non-GPL license has been loaded, this
> - includes modules with no license.
> - Set by modutils >= 2.4.9 and module-init-tools.
> - 2 - A module was force loaded by insmod -f.
> - Set by modutils >= 2.4.9 and module-init-tools.
> - 4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
> - 64 - A module from drivers/staging was loaded.
> + 1 - A module with a non-GPL license has been loaded, this
> + includes modules with no license.
> + Set by modutils >= 2.4.9 and module-init-tools.
> + 2 - A module was force loaded by insmod -f.
> + Set by modutils >= 2.4.9 and module-init-tools.
> + 4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
> + 8 - A module was forcefully unloaded from the system by rmmod -f.
s/forcefully/forcibly/
> + 16 - A hardware machine check error occured on the system.
occurred
> + 32 - A bad page was discovered on the system.
> + 64 - The user has asked that the system be marked "tainted". This
> + could be because they are running software that directly modifies
> + the hardware, or for other reasons.
> + 128 - The system has died.
> + 256 - The ACPI DSDT has been overridden with one supplied by the user
> + instead of using the one provided by the hardware.
> + 512 - A kernel warning has occurred.
> +1024 - A module from drivers/staging was loaded.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-10-18 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 22:55 Greg KH
2008-10-18 8:51 ` Michael Kerrisk [this message]
2008-10-20 20:43 ` Greg KH
2008-10-20 21:37 ` Randy Dunlap
2008-10-20 21:40 ` Greg KH
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=cfd18e0f0810180151v232f623pdbf0f12cad6532d6@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=greg@kroah.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rdunlap@xenotime.net \
--subject='Re: [PATCH] Document kernel taint flags properly' \
/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
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).