summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authoralfred <alfred@FreeBSD.org>2002-01-17 00:12:05 +0000
committeralfred <alfred@FreeBSD.org>2002-01-17 00:12:05 +0000
commit2b493fd00cbf2281e3d7b72202627af22d8f4349 (patch)
treead1a151dea57dfa96b1a62cbccf811f082ecf161 /release
parent04bc01ee42723f18483af5b6574ed87510f00ba2 (diff)
downloadFreeBSD-src-2b493fd00cbf2281e3d7b72202627af22d8f4349.zip
FreeBSD-src-2b493fd00cbf2281e3d7b72202627af22d8f4349.tar.gz
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>
Diffstat (limited to 'release')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud