From:
[email protected]
On Jul 22, Dion Mendel <
[email protected]> wrote:
The deadlock occurs because the advisory locking is for exclusive write.
The purpose of the locking is to stop other processes from writing to
the kernel module file while loading it into the kernel. A shared read
lock will achieve this and remove the above deadlock condition.
No, the purpose is really to lock two concurrents modprobe commands.
By changing using a read lock you are effectively disabling it.
Anyway, this is what I will do in the next upload, because I do not have
a better solution handy.
--
ciao, |
Marco | [7552 caPrZ3Q.xpRGE]
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)