linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <d120d5000703071423n11ade9d7n1852296d70b53d62@mail.gmail.com>
Date:	Wed, 7 Mar 2007 17:23:05 -0500
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: chrdev_open lifetime question

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 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/