From: Dmitry Torokhov <dtor@insightbb.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: chrdev_open lifetime question
Date: Sun, 25 Mar 2007 01:36:25 -0400 [thread overview]
Message-ID: <200703250136.26041.dtor@insightbb.com> (raw)
In-Reply-To: <20070319180225.4638bc80.zaitcev@redhat.com>
Hi Pete,
On Monday 19 March 2007 21:02, Pete Zaitcev wrote:
> On Wed, 7 Mar 2007 17:23:05 -0500, "Dmitry Torokhov" <dmitry.torokhov@gmail.com> wrote:
>
> > It seems that if a process keeps a character device open then other
> > processes will also be able to get into filp->f_op->open(inode,filp)
> > in chrdev_open() even after a driver called cdev_del() as part of its
> > unwind procedure. Is this correct or am I missing something?
>
> I see no replies in the archives. Have you got any private ones?
No I have not.
>
> Also, what's the context?
I want to switch input handlers to cdevs to rip table of devices out
of input core and lift limit on potential number of devices and was
pondering locking implications.
--
Dmitry
prev parent reply other threads:[~2007-03-25 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 22:23 chrdev_open lifetime question Dmitry Torokhov
2007-03-20 1:02 ` Pete Zaitcev
2007-03-25 5:36 ` Dmitry Torokhov [this message]
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=200703250136.26041.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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.