I have fixed the problem by commenting out the bug throwing line in the kernel source:
--- fs/inode.c 2010-07-08 11:23:05.243232762 +0200 +++ fs/inode.c 2010-07-05 14:29:41.599608689 +0200 @@ -320,7 +320,8 @@ might_sleep(); invalidate_inode_buffers(inode);
- BUG_ON(inode->i_data.nrpages); +/* stk 20100705 nbsp GmbH fix inode/fuse fuck + BUG_ON(inode->i_data.nrpages); */ BUG_ON(!(inode->i_state & I_FREEING)); BUG_ON(inode->i_state & I_CLEAR); inode_sync_wait(inode);
As far as I can see, this is a false alarm on behalf of inode.c. Right?
I have fixed the problem by commenting out the bug throwing line in the kernel source:
--- fs/inode.c 2010-07-08 11:23:05.243232762 +0200 inode_buffers( inode);
+++ fs/inode.c 2010-07-05 14:29:41.599608689 +0200
@@ -320,7 +320,8 @@
might_sleep();
invalidate_
- BUG_ON( inode-> i_data. nrpages) ; inode-> i_data. nrpages) ; */ !(inode- >i_state & I_FREEING)); inode-> i_state & I_CLEAR); sync_wait( inode);
+/* stk 20100705 nbsp GmbH fix inode/fuse fuck
+ BUG_ON(
BUG_ON(
BUG_ON(
inode_
As far as I can see, this is a false alarm on behalf of inode.c. Right?