Messages in this thread |  | | Subject | Re: [NFS] [PATCH] Re: grow_inodes: inode-max limit reached - how to find/fix the inode leak? | From | Trond Myklebust <> | Date | 31 Aug 2000 15:23:43 +0200 |
| |
>>>>> " " == Michael Riepe <michael@stud.uni-hannover.de> writes:
> There is an inode leak in lockd, caused by a reference counting > bug. It will appear when you use DOS/Windows clients to access > a knfsd+lockd based NFS server, and it will crash the server > sooner or later (a DOS attack, literally ;). The lockd bug is > still alive in 2.4.0-test?, so upgrading doesn't help either.
> I'll attach my patch for 2.2.16. It should apply to > 2.4.0-test? too, with one or two lines of fuzz maybe.
Hi Michael,
Your patch does not seem correct to me. IMO you should rather be calling nlm_release_file() in both cases where you applied 'put_file()'.
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |