summaryrefslogtreecommitdiff
path: root/sys/net/bsd-comp.c
diff options
context:
space:
mode:
authorArtur Grabowski <art@cvs.openbsd.org>2009-07-28 11:19:44 +0000
committerArtur Grabowski <art@cvs.openbsd.org>2009-07-28 11:19:44 +0000
commitae8201f41dd5672238a8adea17dccfada1b34d7a (patch)
tree6d116943e52a30e5450fc01d2208b8033ed389b8 /sys/net/bsd-comp.c
parentb0ae489e273a60d3f8e2cb8a774d86b1a433f411 (diff)
Using the buf pointer returned from incore is a really bad idea.
Even if we know that someone safely holds B_BUSY and will not modify the buf (as was the case in here), we still need to be sure that the B_BUSY will not be released while we fiddle with the buf. In this case, it was not safe, since copyout can sleep and whoever was writing out the buf could finish the write and release the buf which could then get recycled or unmapped while we slept. Always acquire B_BUSY ourselves, even when it might give a minor performance penalty. thib@ ok
Diffstat (limited to 'sys/net/bsd-comp.c')
0 files changed, 0 insertions, 0 deletions