summaryrefslogtreecommitdiff
path: root/etc/rbootd.conf
diff options
context:
space:
mode:
authorDavid Gwynne <dlg@cvs.openbsd.org>2010-12-07 00:44:49 +0000
committerDavid Gwynne <dlg@cvs.openbsd.org>2010-12-07 00:44:49 +0000
commit281f5823f1e95cc6a64d16e6f386b170ca4dfda3 (patch)
tree17b099676200ba95500467b7daa686da092d1fb8 /etc/rbootd.conf
parentc6ff01bb8cc597758e9b06095e682bae725e888c (diff)
bring src/sys/arch/amd64/amd64/dkcsum.c r1.16 over to i386:
the boot loader passes a variable that identifies the disk its booting off made up of a bunch of fields like adapter, controller, disk, and partition offsets, plus a table of all the disks it can see which includes this id and a checksum. the kernel goes through and checksums the disks and then maps that back to the id associated with that disk, and then compares some of the fields in those ids against the boot disks id to figure out which disk its on. the problem is we overflow one of those fields (the disk id one). since the other fields are set to 0 by the boot loader, this doesnt really matter that much. however, since those fields are now significant because of the overflow, we should compare them too. this prevents sd16 being matched as the boot disk after sd0 on my system with 25 disks attached. ok krw@ weingart@ ithe boot loader passes a variable that identifies the disk its booting off made up of a bunch of fields like adapter, controller, disk, and partition offsets, plus a table of all the disks it can see which includes this id and a checksum. the kernel goes through and checksums the disks and then maps that back to the id associated with that disk, and then compares some of the fields in those ids against the boot disks id to figure out which disk its on. the problem is we overflow one of those fields (the disk id one). since the other fields are set to 0 by the boot loader, this doesnt really matter that much. however, since those fields are now significant because of the overflow, we should compare them too. this prevents sd16 being matched as the boot disk after sd0 on my system with 25 disks attached. requested by deraadt@ ok krw@ weingart@
Diffstat (limited to 'etc/rbootd.conf')
0 files changed, 0 insertions, 0 deletions