lkml.org 
[lkml]   [1997]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: 2.0.31-1 patch: possible fix for some inode problems
On Sun, 9 Nov 1997, Nathan Bryant wrote:

> [snip]
>
> Tried your patch. I'm getting tons of "VFS: clear_inode called on unlocked
> inode." messages.

Are you using MD? If so you can safely ignore the message - I just wanted
to see if any of the filesystems were doing anything silly. The following
patch 'll take care of it and still let the message come through.
Alternatively, just comment out the printk in clear_inode (as it locks the
inode if it wasn't).

-ben

--- lin-ben/drivers/block/md.c.orig Sat Jun 29 17:04:00 1996
+++ lin-ben/drivers/block/md.c Sun Nov 9 16:57:37 1997
@@ -215,8 +215,10 @@
}

/* Remove locks. */
- for (i=0; i<md_dev[minor].nb_dev; i++)
+ for (i=0; i<md_dev[minor].nb_dev; i++) {
+ md_dev[minor].devices[i].inode->i_lock = 1;
clear_inode (md_dev[minor].devices[i].inode);
+ }

md_dev[minor].nb_dev=md_size[minor]=0;
md_hd_struct[minor].nr_sects=0;


\
 
 \ /
  Last update: 2005-03-22 13:40    [W:0.055 / U:2.488 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site