Hi Pete,
On Monday 19 March 2007 21:02, Pete Zaitcev wrote:
> On Wed, 7 Mar 2007 17:23:05 -0500, "Dmitry Torokhov" <[EMAIL PROTECTED]>
> 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)
> >
Hi Pete,
On Monday 19 March 2007 21:02, Pete Zaitcev wrote:
On Wed, 7 Mar 2007 17:23:05 -0500, Dmitry Torokhov [EMAIL PROTECTED]
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
On Wed, 7 Mar 2007 17:23:05 -0500, "Dmitry Torokhov" <[EMAIL PROTECTED]> 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
>
On Wed, 7 Mar 2007 17:23:05 -0500, Dmitry Torokhov [EMAIL PROTECTED] 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
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
-
To
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
-
To
6 matches
Mail list logo