[lkml]   [2009]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3] vfs: new O_NODE open flag
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?


 \ /
  Last update: 2009-12-07 13:43    [W:0.081 / U:65.376 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site