public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marty Leisner" <mleisner@eng.mc.xerox.com>
To: linux-kernel@vger.kernel.org
Cc: leisner@rochester.rr.com
Subject: kernel threads and close method in a device driver
Date: Tue, 17 Apr 2001 17:04:28 -0400	[thread overview]
Message-ID: <200104172104.RAA08013@mailhost.eng.mc.xerox.com> (raw)


I'm involved with modifying a device driver for new hardware.

The architecture is currently:

	open device
	do IOCTL (spinning a kernel thread and doing initialization)

There is currently an IOCTL which short-circuits to the close method.
Turns out it seems necessary to do this IOCTL -- close never gets 
invoked.

What can cause a close not to get invoked?  BTW, the close is returning
with a 0 status to the application ...(it definitely did NOT 
get invoked in the driver)

In ps:
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040 33839   750     1   7   0  1064  348 end    D    pts/2      0:00 ./openinit
040 33839   630     1   0   0  1064  348 end    D    pts/0      0:00 ./openinit

These are the kernel threads which won't go away.

I'm running 2.2.12 with the bigphysarea patch...

(leave my work address on the distribution -- I get linux kernel at home...)

marty		mleisner@eng.mc.xerox.com   
Don't  confuse education with schooling.
	Milton Friedman to Yogi Berra

             reply	other threads:[~2001-04-17 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 21:04 Marty Leisner [this message]
2001-04-17 21:37 ` kernel threads and close method in a device driver Alan Cox
2001-04-17 21:43 ` Andi Kleen
2001-04-17 23:32 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20 18:54 Marty Leisner

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=200104172104.RAA08013@mailhost.eng.mc.xerox.com \
    --to=mleisner@eng.mc.xerox.com \
    --cc=leisner@rochester.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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