oops: 2.5.51 lock_get_status
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.43.0212130942110.31117-100000@morpheus
Burton Windle, Fri, Dec 13, 2002 15:42:20 +0100:
Quoted 4 lines
This might also be of interest...
http://marc.theaimsgroup.com/?l=linux-kernel&m=103825968004879&w=2
hmm... This:
| note, do not use NFS when using this patch. really; i mean it. somehow | i managed to corrupt thread_info.cpu causing _udelay_ to oops.
doesn't look very encouraging.
Maybe there is already some news about it?
I volunteer to test anything :)
as being hit by the bug.
-alex
Quoted 19 lines · Alex Riesen
Quoted 18 lines
Burton Windle, Fri, Dec 13, 2002 15:08:45 +0100:
Quoted 2 lines
Oh, thanks. Still fogetting about the new thing to look before.
Quoted 10 lines · Alex Riesen
Quoted 9 lines
2.5.51+bk as of 12 Dec 23:00 CET.
tried to strace(4.4) the d4x with follow-fork mode. d4x is a multi-threaded app using posix advisory locks.
(http://www.krasu.ru/soft/chuchelo/)The thing calls fcntl, which fails as if the file were locked: