Alfred Perlstein 4b4ec9b800 Fix boundry condition in lock management: ... Alfred, I took a look at retry_blockingfilelocklist() and the solution seemed simple enough. Please correct me if I am wrong. It seems said routine doesn't take into account boundary conditions when putting back file_lock entries into the blocked lock-list. Specifically, it fails when the file_lock being put back is the last element in the list, and when it is the only element in the list. I've included a patch below. Basically, it introduces another variable: pfl, which keeps track of the list item before ifl. That way if nfl is NULL, ifl gets inserted after pfl. If pfl is also NULL, then it gets inserted at the head of the list (since it was the only element in the list). Submitted by: Mike Makonnen <mike_makonnen@yahoo.com> Tested by: Thomas Quinot <thomas@cuivre.fr.eu.org>		2002-01-17 00:12:05 +00:00
..
kern.c	Fixup for WARNS.	2001-11-12 16:29:45 +00:00
lock_proc.c	Turn on NO_WERROR and set WARNS to 1.	2001-11-13 11:24:23 +00:00
lockd_lock.c	Fix boundry condition in lock management:	2002-01-17 00:12:05 +00:00
lockd_lock.h	Turn on NO_WERROR and set WARNS to 1.	2001-11-13 11:24:23 +00:00
lockd.c	Bring in Andrew P. Lentvorski initial work on making lockd work,	2001-11-15 09:35:51 +00:00
lockd.h	Bring in Andrew P. Lentvorski initial work on making lockd work,	2001-11-15 09:35:51 +00:00
Makefile	Turn on NO_WERROR and set WARNS to 1.	2001-11-13 11:24:23 +00:00
rpc.lockd.8
test.c