summaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authordim <dim@FreeBSD.org>2016-12-18 14:31:11 +0000
committerdim <dim@FreeBSD.org>2016-12-18 14:31:11 +0000
commite816a19b7fe4c32d33a3efa97be3a4539dd5b79c (patch)
tree0d8cabeba5fd2e1f7355f37fc07d3974f6a9b11e /tests
parentb352adc836074b759a03e038c5e887c8dbf0d6c6 (diff)
downloadFreeBSD-src-e816a19b7fe4c32d33a3efa97be3a4539dd5b79c.zip
FreeBSD-src-e816a19b7fe4c32d33a3efa97be3a4539dd5b79c.tar.gz
MFC r310013 (by cperciva):
Check that blkfront devices have a non-zero number of sectors and a non-zero sector size. Such a device would be a virtual disk of zero bytes; clearly not useful, and not something we should try to attach. As a fortuitous side effect, checking that these values are non-zero here results in them not *becoming* zero later on the function. This odd behaviour began with r309124 (clang 3.9.0) but is challenging to debug; making any changes to this function whatsoever seems to affect the llvm optimizer behaviour enough to make the unexpected zeroing of the sector_size variable cease. PR: 215209 Security: The potential for variables to unexpectedly become zero has worrying consequences for security in general, but not so much in this particular context. MFC r310086: In xbd_connect(), use correct scanf conversion specifiers for the feature_barrier and feature_flush variables. Otherwise, adjacent variables on the stack, such as sector_size, may be overwritten, with disastrous results. Note that I did not see a good reason to revert the addition of zero checks introduced in r310013. Better safe than sorry. PR: 215209 Tested by: royger
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud