Messages in this thread | | | Subject | Re: [PATCH v3] vfs: new O_NODE open flag | From | Miklos Szeredi <> | Date | Mon, 07 Dec 2009 13:41:09 +0100 |
| |
On Mon, 7 Dec 2009, Alan Cox wrote: > The standard udev unload is a true open barrier so has an implicit > revoke() caused by the fact you cannot keep a handle to the filename open > during the udev sequence (or the old driver would be pinned by a refcount > and not unload).
True, udev unload is an open barrier (modulo races), but O_NODE opens simply don't matter in this respect, because they don't have anything to do with the driver.
ln /dev/foo /dev/shm/my_secret_device_link (foo is removed) open("/dev/shm/my_secret_device_link", O_RDWR)
How is this different than keeping the device open with O_NODE?
Thanks, Miklos
| |