All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Probable module bug in linux-2.6.5-1.358
Date: Thu, 07 Oct 2004 10:25:34 -0700	[thread overview]
Message-ID: <1097169934.29576.4.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0410070850480.10751@chaos.analogic.com>

Still haven't full source so this is still guess work.
But assuming it is a character device, did you forget to add an owner
field to the file ops structure?

static struct file_operations xxx_fops = {
	.owner	= THIS_MODULE,
	.read	= my_read,
...

The owner field is used by the character device layer to maintain module
ref counts in 2.6.




  reply	other threads:[~2004-10-07 17:28 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
     [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 [this message]
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=1097169934.29576.4.camel@localhost.localdomain \
    --to=shemminger@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.