summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authoriedowse <iedowse@FreeBSD.org>2002-10-30 19:08:56 +0000
committeriedowse <iedowse@FreeBSD.org>2002-10-30 19:08:56 +0000
commit94318a914fff31084d6a418582cbea4340d294fc (patch)
tree72b9d551d9e9c569f21d7c9ea55ad3a05f651a7f /lib/libc
parent122a6b9ad2a52d909b8df15d6f593b8aaf8dcf55 (diff)
downloadFreeBSD-src-94318a914fff31084d6a418582cbea4340d294fc.zip
FreeBSD-src-94318a914fff31084d6a418582cbea4340d294fc.tar.gz
Revision 1.136 introduced two features that may cause undefined
behaviour of the hardware: a possibly reserved bit of the receive descriptor (RFA) `status' field is borrowed to record no-resource (RNR) events, and the same status field is read and written to at a time that may clash with the hardware updating this field. There is no hardware documentation available to determine if these things are safe to do; the second issue almost certainly isn't, and the first is only safe if there is documentation saying that this bit is free to be used by the driver. The PR referenced below provides extremely convincing evidence that the changes cause random crashes on some (unusual) hardware. Since these features are only required by the DEVICE_POLLING case, this commit makes their use conditional on that option. It does not change the DEVICE_POLLING case, but at least people with the rare hardware on which this code causes problems can now avoid the crashes by not enabling DEVICE_POLLING. PR: kern/42260 Reviewed by: luigi Problem revision found by: Pawel Malachowski <pawmal@unia.3lo.lublin.pl> Tested by: Pawel Malachowski <pawmal@unia.3lo.lublin.pl> MFC after: 1 week
Diffstat (limited to 'lib/libc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud