Revision b37b03b7051493c9f9a6b336c9c0f81334885b7d authored by Trond Myklebust on 25 November 2005, 22:10:06 UTC, committed by Trond Myklebust on 25 November 2005, 22:11:29 UTC
In cases where the server has gone insane, nfs_update_inode() may end up calling nfs_invalidate_inode(), which again calls stuff that takes the inode->i_lock that we're already holding. In addition, given the sort of things we have in NFS these days that need to be cleaned up on inode release, I'm not sure we should ever be calling make_bad_inode(). Fix up spinlock recursion, and limit nfs_invalidate_inode() to clearing the caches, and marking the inode as being stale. Thanks to Steve Dickson <SteveD@redhat.com> for spotting this. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
1 parent ff60406
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 18.1 KB |
| Makefile | -rw-r--r-- | 921 bytes |
| calibrate.c | -rw-r--r-- | 4.7 KB |
| do_mounts.c | -rw-r--r-- | 9.0 KB |
| do_mounts.h | -rw-r--r-- | 1.7 KB |
| do_mounts_devfs.c | -rw-r--r-- | 2.8 KB |
| do_mounts_initrd.c | -rw-r--r-- | 3.0 KB |
| do_mounts_md.c | -rw-r--r-- | 7.6 KB |
| do_mounts_rd.c | -rw-r--r-- | 10.0 KB |
| initramfs.c | -rw-r--r-- | 10.0 KB |
| main.c | -rw-r--r-- | 17.1 KB |
| version.c | -rw-r--r-- | 748 bytes |
Computing file changes ...
