chrdev_open lifetime question

LKML Archive on lore.kernel.org
help / color / mirror / Atom feed

* chrdev_open lifetime question
@ 2007-03-07 22:23 Dmitry Torokhov
  2007-03-20  1:02 ` Pete Zaitcev
  0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Torokhov @ 2007-03-07 22:23 UTC (permalink / raw)
  To: linux-kernel

Hi,

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?

Thanks!

-- 
Dmitry

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: chrdev_open lifetime question
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Pete Zaitcev @ 2007-03-20  1:02 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-kernel

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?

Also, what's the context?

-- Pete

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: chrdev_open lifetime question
  2007-03-20  1:02 ` Pete Zaitcev
@ 2007-03-25  5:36   ` Dmitry Torokhov
  0 siblings, 0 replies; 3+ messages in thread
From: Dmitry Torokhov @ 2007-03-25  5:36 UTC (permalink / raw)
  To: Pete Zaitcev; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-03-25  5:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).