Re: 2.4.15-pre9 breakage (inode.c)

Jeff Merkey
2001-11-23T21:44:33Z

Al,

I have seen this as well during testing, except in my case, it results in a
hard hang of sorts that does not respond to signals. I can make it show up
easily by doing a copy accross mount points in low memory conditions, if any
of this helps. Sounds like you've got a good handle on it, though.

Jeff

----- Original Message -----
From: "Alexander Viro" <viro@math.psu.edu>
To: <linux-kernel@vger.kernel.org>
Cc: "Linus Torvalds" <torvalds@transmeta.com>; "Marcelo Tosatti"
<marcelo@conectiva.com.br>
Sent: Friday, November 23, 2001 2:22 PM
Subject: 2.4.15-pre9 breakage (inode.c)

> Sigh... Supposed fix to problems with stale inodes was completely
> broken.
>
> What we need is "if we are doing last iput() on fs that is getting
> shut, sync it and don't leave it in cache". And yes, we have a similar
> path in iput(). Similar, but not quite the same.
>
> Fix is
> * new fs flag: "MS_ACTIVE".
> * set after normal ->read_super().
> * reset after we are done with fsync_super() in kill_super().
> * iput() checking that and if it's set - doing write_inode_now() and
kicking
> it out of hash.
>
> I'll send patch in ~10 minutes.
>
> -
> 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/