David Malone wrote: > A child process seems to be able to let go of a parent's lock on > 4.0 by closing a file discriptor, the same doesn't seem to be true > on 3.3. So, apparently, it was broken in rev. 1.68 of kern_descript.c. (Another example that comments (in closef() in this case) serve no purpose :-/). BTW, I have another little concern with that commit: It make possible for last close() of a file descriptor to return 0 instead of the error from VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. Dima To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Serious locking problem in CURRENT Ollivier Robert
- Re: Serious locking problem in CURRENT Ollivier Robert
- Re: Serious locking problem in CURRENT David O'Brien
- Re: Serious locking problem in CURRENT David Malone
- Re: Serious locking problem in CURR... Dmitrij Tejblum
- Re: Serious locking problem in ... Brian Fundakowski Feldman
- Re: Serious locking proble... Dmitrij Tejblum
- Re: Serious locking pr... Brian Fundakowski Feldman
- Re: Serious locking problem in CURRENT Jonathan Lemon
- Re: Serious locking problem in CURRENT Ollivier Robert
- Re: Serious locking problem in CURR... David Malone
- Re: Serious locking problem in ... Ollivier Robert
- Re: Serious locking problem in CURRENT David Malone
- Re: Serious locking problem in CURR... Ben Smithurst
- Re: Serious locking problem in ... David Malone