summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authormjacob <mjacob@FreeBSD.org>2001-06-14 17:13:24 +0000
committermjacob <mjacob@FreeBSD.org>2001-06-14 17:13:24 +0000
commit1c41b07fa5158bd854f75b029650f76216a4915f (patch)
tree5d6ba01421b751dd04a5d15ccd9c19e55261b97f /release
parent65ed101d3ca9a6904711608c3e602218a4cdafc5 (diff)
downloadFreeBSD-src-1c41b07fa5158bd854f75b029650f76216a4915f.zip
FreeBSD-src-1c41b07fa5158bd854f75b029650f76216a4915f.tar.gz
We've had problems with data corruption occuring on
commands that complete (with no apparent error) after we receive a LIP. This has been observed mostly on Local Loop topologies. To be safe, let's just mark all active commands as dead if we get a LIP and we're on a private or public loop. MFC after: 4 weeks
Diffstat (limited to 'release')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud