From: Paolo Ornati <ornati@fastwebnet.it>
To: sasa.ostrouska@volja.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops in 2.6.14-rc3
Date: Sat, 8 Oct 2005 09:14:16 +0200 [thread overview]
Message-ID: <20051008091416.6038ebaa@localhost> (raw)
In-Reply-To: <1128731551.8004.2.camel@rc-vaio.rcdiostrouska.com>
On Sat, 08 Oct 2005 02:32:31 +0200
Sasa Ostrouska <sasa.ostrouska@volja.net> wrote:
> Oct 8 02:20:33 rc-vaio kernel: EIP: 0060:[<c01eac19>] Tainted: P
http://www.tux.org/lkml/#s1-18
"Some vendors distribute binary modules (i.e. modules without available
source code under a free software license). As the source is not freely
available, any bugs uncovered whilst such modules are loaded cannot be
investigated by the kernel hackers. All problems discovered whilst such
a module is loaded must be reported to the vendor of that module, not
the Linux kernel hackers and the linux-kernel mailing list. The
tainting scheme is used to identify bug reports from kernels with
binary modules loaded: such kernels are marked as "tainted" by means of
the MODULE_LICENSE tag. If a module is loaded that does not specify an
approved license, the kernel is marked as tainted. The canonical list
of approved license strings is in linux/include/linux/module.h. "oops"
reports marked as tainted are of no use to the kernel developers and
will be ignored. A warning is output when such a module is loaded. Note
that you may come across module source that is under a compatible
license, but does not have a suitable MODULE_LICENSE tag. If you see a
warning from modprobe or insmod for a module under a compatible
license, please report this bug to the maintainers of the module, so
that they can add the necessary tag."
--
Paolo Ornati
Linux 2.6.14-rc3-gc0758146 on x86_64
next prev parent reply other threads:[~2005-10-08 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 0:32 oops in 2.6.14-rc3 Sasa Ostrouska
2005-10-08 1:48 ` Grant Coady
2005-10-08 13:04 ` Sasa Ostrouska
2005-10-08 7:14 ` Paolo Ornati [this message]
2005-10-23 13:05 ` Sasa Ostrouska
2005-10-23 14:22 ` Adam Kropelin
2005-10-23 14:31 ` Sergey Vlasov
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=20051008091416.6038ebaa@localhost \
--to=ornati@fastwebnet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=sasa.ostrouska@volja.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox