linux-kernel - Re: chrdev_open lifetime question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200703250136.26041.dtor@insightbb.com>
Date:	Sun, 25 Mar 2007 01:36:25 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: chrdev_open lifetime question

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@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/