{"push_id":1279852599,"size":4,"distinct_size":4,"ref":"refs/heads/releng/11.0","head":"2ff56da569941d069a3e6d5b36753d6e1d38e6dd","before":"89593f020ab4c0dd2e6acd96b80fe745b44ea1a1","commits":[{"sha":"68ba0baa1f30fc67bea58f03e0aae8df30aa5f72","author":{"name":"gjb","email":"7e40ed87ec97d473d751547d91253384f0f9af61@FreeBSD.org"},"message":"Add an 'Important Notes' section before the 'Upgrading' section.\n\nDocument OpenSSH DSA key deprecation and removal of Protocol 1\nsupport.\n\nApproved by:\tre (implicit, relnotes)\nSponsored by:\tThe FreeBSD Foundation","distinct":true,"url":"https://api.github.com/repos/Crest/freebsd/commits/68ba0baa1f30fc67bea58f03e0aae8df30aa5f72"},{"sha":"b7f8b4ed395f76bdc591ff346a4e8ec165265e3e","author":{"name":"gjb","email":"7e40ed87ec97d473d751547d91253384f0f9af61@FreeBSD.org"},"message":"MFS11 305232:\nMFC r304966 (peter):\n The read-ahead code from r298230 made it likely the boot code would read\n beyond the end of disk. r298900 added code to prevent this.  Some BIOSes\n cause significant delays if asked to read past end-of-disk.\n\n We never trusted the BIOS to accurately report the sectorsize of disks\n before and this set of changes.  Unfortuately they interact badly with\n the infamous >2TB wraparound bugs.  We have a number of relatively-recent\n machines in the FreeBSD.org cluster where the BIOS reports 3TB disks as 1TB.\n\n With pre-r298900 they work just fine.  After r298900 they stop working if\n the boot environment attempts to access anything outside the first 1TB on\n the disk.  'ZFS: I/O error, all block copies unavailable' etc.  It affects\n both UFS and ZFS if they try to boot from large volumes.\n\n This change replaces the blind trust of the BIOS end-of-disk reporting\n with a read-ahead clip to prevent reads crossing the of end-of-disk\n boundary.  Since 2^32 (2TB) size reporting truncation is not uncommon,\n the clipping is done on 2TB aliases of the reported end-of-disk.\n ie: a 3TB disk reported as 1TB has readahead clipped at 1TB, 3TB, 5TB, ...\n as one of them is likely to be the real end-of-disk.\n\n This should make the loader on these broken machines behave the same as\n traditional pre-r298900 loader behavior, without disabling read-ahead.\n\nPR:\t\t212139\nApproved by:\tre (kib)\nSponsored by:\tThe FreeBSD Foundation","distinct":true,"url":"https://api.github.com/repos/Crest/freebsd/commits/b7f8b4ed395f76bdc591ff346a4e8ec165265e3e"},{"sha":"d6d6b83dfe62f01d1f8803be5c0dfc1b243d332c","author":{"name":"nwhitehorn","email":"ad260e4b296274ef4bee3941ce4f620e4656a42f@FreeBSD.org"},"message":"MFS11 r305249:\nMFC r305036:\n\nSome versions of SLOF do not append the partition number to the boot\ndevice argument to the stage-1 bootloader. In such cases, boot1 would\nonly try to read the entire device rather than checking for partitions.\nInstead of panic'ing, fall back to reading the partitions as normal in\nsuch situations. This was preventing boot of installed systems on some\nversions of PowerKVM.\n\nPR:\t\tkern/211599\nApproved by:\tre (gjb)","distinct":true,"url":"https://api.github.com/repos/Crest/freebsd/commits/d6d6b83dfe62f01d1f8803be5c0dfc1b243d332c"},{"sha":"2ff56da569941d069a3e6d5b36753d6e1d38e6dd","author":{"name":"nwhitehorn","email":"ad260e4b296274ef4bee3941ce4f620e4656a42f@FreeBSD.org"},"message":"MFS11 r305250:\nMFC r305108,305109:\nRefix operation on sparse CPU mappings as in r302372, temporarily broken\nby r304716.\n\nPR:\t\tkern/210106\nApproved by:\tre (gjb)","distinct":true,"url":"https://api.github.com/repos/Crest/freebsd/commits/2ff56da569941d069a3e6d5b36753d6e1d38e6dd"}]}
{"actor":{"display_login":"Crest"}}