summaryrefslogtreecommitdiffstats
path: root/bin/dd
diff options
context:
space:
mode:
authormjacob <mjacob@FreeBSD.org>1999-06-19 19:33:44 +0000
committermjacob <mjacob@FreeBSD.org>1999-06-19 19:33:44 +0000
commit63ed685667d63c71e409de1ac005284dad01bf15 (patch)
tree8a53ca5d7084c98c736a44dea61c9a22897f437a /bin/dd
parent280f8f95b4045e45c9f5d18632bd0ccb8cc0fad2 (diff)
downloadFreeBSD-src-63ed685667d63c71e409de1ac005284dad01bf15.zip
FreeBSD-src-63ed685667d63c71e409de1ac005284dad01bf15.tar.gz
Thanks to Bruce for noticing this.... compare against the *new* nfsnode's
mount point for seeing whether or not the new nfsnode is already in the hash queue. We're pretty much guaranteed that the old nfsnode is already in the hash queue. Wank! Infinite Loop! Looks like just a minor typo.... (ah the influence of fortran ... np && np2... why not nfsnode_the_first && nfsnode_the_second???)...
Diffstat (limited to 'bin/dd')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud