Messages in this thread Patch in this message | | | Subject | Re: panic - Attempting to free lock with active block list | From | Trond Myklebust <> | Date | Wed, 05 Jan 2005 22:54:03 +0100 |
| |
on den 05.01.2005 Klokka 12:32 (-0800) skreiv Chris Wright: > * Jan-Frode Myklebust (Jan-Frode.Myklebust@bccs.uib.no) wrote: > > We have a couple of mail-servers running first 2.6.9-1.681_FC3smp > > and was later upgraded to the Fedora test kernel 2.6.10-1.727_FC3smp > > which I think is pretty plain 2.6.10 + ac2. But they both keep > > crashing with the message: > > > > Kernel panic - not syncing: Attempting to free lock with active block list > > > > Any ideas how to attack this?
Well, the prevailing theory tends to start along the lines of "find out how to reproduce the problem...". ;-)
Looking at the NFS code, I can attempt a wild guess about what may be happening: there may be a race when pressing ^C in the middle of a blocking NFS lock RPC call, and if so, the following patch will fix it.
Try it, and see whether or not it fixes your problem, but if it doesn't, then I agree with Chris' suggestion of replacing those "panic()" calls with BUG_ON()s.
Cheers, Trond
file.c | 2 +- 1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.10/fs/nfs/file.c =================================================================== --- linux-2.6.10.orig/fs/nfs/file.c +++ linux-2.6.10/fs/nfs/file.c @@ -374,7 +374,7 @@ static int do_setlk(struct file *filp, i * the process exits. */ if (status == -EINTR || status == -ERESTARTSYS) - posix_lock_file(filp, fl); + posix_lock_file_wait(filp, fl); } else status = posix_lock_file_wait(filp, fl); unlock_kernel();
-- Trond Myklebust <trond.myklebust@fys.uio.no>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |