From: Arjan van de Ven <arjanv@redhat.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Probable module bug in linux-2.6.5-1.358
Date: Thu, 07 Oct 2004 11:59:04 +0200 [thread overview]
Message-ID: <1097143144.2789.19.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410061807030.4586@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Thu, 2004-10-07 at 00:08, Richard B. Johnson wrote:
> The attached script shows that an attempt to open a device
> after its module was removed, will seg-fault the kernel.
Oct 6 17:03:30 chaos kernel: Analogic Corp Datalink Driver : Module
removed
Oct 6 17:03:38 chaos kernel: EIP: 0060:[<021556ad>] Not tainted
Oct 6 17:03:38 chaos kernel: EFLAGS: 00010206 (2.6.5-1.358-noreg)
since your module apparently is gpl (the kernel isn't tainted), can you
post a URL to the sourcecode so that we can point the bug out to you ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-07 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 22:08 Probable module bug in linux-2.6.5-1.358 Richard B. Johnson
2004-10-06 23:20 ` Stephen Hemminger
2004-10-06 22:38 ` Alan Cox
2004-10-06 23:22 ` Stephen Hemminger
2004-10-07 11:50 ` Richard B. Johnson
2004-10-07 9:59 ` Arjan van de Ven [this message]
[not found] ` <Pine.LNX.4.61.0410070753060.9988@chaos.analogic.com>
2004-10-07 12:17 ` Arjan van de Ven
2004-10-07 12:26 ` Richard B. Johnson
2004-10-07 12:28 ` Arjan van de Ven
2004-10-07 12:34 ` Richard B. Johnson
2004-10-07 12:57 ` Richard B. Johnson
2004-10-07 17:25 ` Stephen Hemminger
2004-10-07 18:25 ` Richard B. Johnson
2004-10-07 19:05 ` Stephen Hemminger
2004-10-07 18:59 ` Alan Cox
2004-10-07 20:27 ` Stephen Hemminger
2004-10-07 20:48 ` Richard B. Johnson
2004-10-07 21:35 ` Valdis.Kletnieks
2004-10-07 22:09 ` Stephen Hemminger
2004-10-07 19:12 ` Richard B. Johnson
2004-10-07 19:27 ` Richard B. Johnson
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=1097143144.2789.19.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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