projects / dragonfly.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7ae4ac3) | patch
One of the lf_create_range() calls in lf_clearlock() was passing a bogus
authorMatthew Dillon <dillon@dragonflybsd.org>
Fri, 7 May 2004 05:45:31 +0000 (05:45 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Fri, 7 May 2004 05:45:31 +0000 (05:45 +0000)
commit2c4af4c44923c20d913269b9e59e8f192c0a24bb
tree5c5d62108c2d03b88e1b9dfc51143eb61c9e191etree | snapshot
parent7ae4ac37cd1c0536cbbd565a0c81e81c71c301d0commit | diff
One of the lf_create_range() calls in lf_clearlock() was passing a bogus
owner (nrange->lf_owner instead of range->lf_owner), causing a panic
later on.  'atq now' triggers the panic.  This minor bug was introduced in
the recent fix to the malloc blocking issues.

Noticed-by: David Rhodus <drhodus@machdep.com>
sys/kern/kern_lockf.c diff | blob | blame | history
DragonFly Project Source