[lkml]   [2000]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] For 2.4: syscall revoke.
> 	1) one process does read() on device, another does revoke()
> followed by rmmod. Oops - nothing holds module in memory, the first
> process is executing code from that module (->read(), that is) and
> we unmap that code.
> 2) every access to ->f_op suddenly becomes unsafe. Basically the
> same scenario, but here we have the window between fetching ->f_op and
> calling ->f_op->foo. You have no exclusion here, and even if you had, you
> still got #1 to deal with.

Is #2 actually a problem if #1 is ok. We don't destroy f_ops tables except
on a module unload. Another thing that is arguable is that revoke() should
not return until the revocation is completed. That would solve #1 in the
process I belive ?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.069 / U:3.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site