FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=upstream%2F12.1.0 2019-11-01T00:00:17Z 2019-11-01T00:00:17Z Glen Barber gjb@FreeBSD.org 2019-11-01T00:00:17Z urn:sha1:cc807f9e55c25fe811f7db5d1540455ff2bf8716 - Add the anticipated 12.1-RELEASE date to UPDATING. - Set a static __FreeBSD_version. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) 2019-10-25T18:46:53Z Michael Tuexen tuexen@FreeBSD.org 2019-10-25T18:46:53Z urn:sha1:16981b16f338577fa04c1eac9b41f5b53a5a5c63 Ensure that the flags indicating IPv4/IPv6 are not changed by failing bind() calls. This would lead to inconsistent state resulting in a panic. A fix for stable/11 was committed in https://svnweb.freebsd.org/base?view=revision&revision=338986 Reported by: syzbot+2609a378d89264ff5a42@syzkaller.appspotmail.com Obtained from: jtl@ Sponsored by: Netflix, Inc. Approved by: re (gjb@) 2019-10-21T17:17:21Z Glen Barber gjb@FreeBSD.org 2019-10-21T17:17:21Z urn:sha1:3f53a11e190819aa61dd11db4c3dd8eb02e4a2ad Follow up on r351916 by also bumping the version suffix to 12.1 in Makefile.libcompat. Approved by: re (kib) Sponsored by: Rubicon Communications, LLC (Netgate) 2019-10-18T00:00:11Z Glen Barber gjb@FreeBSD.org 2019-10-18T00:00:11Z urn:sha1:27cbd813d3cbeabe67fb35e0f3a5b66efbf6f52a cycle. - Update the dvd1.iso pkg(8) configuration to use the release_1 package set to populate the dvd. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) 2019-10-17T16:20:24Z Ian Lepore ian@FreeBSD.org 2019-10-17T16:20:24Z urn:sha1:81b600616a9046d6d124cacfc822c85a185dfc02 r353651: Relax the sdhci(4) check that filters out the 1.8v voltage option unless the slot is flagged as 'embedded'. The features related to embedded and shared slots were added in v3.0 of the sdhci spec. Hardware prior to v3 sometimes supported 1.8v on non- removable devices in embedded systems, but had no way to indicate that via the standard sdhci registers (instead they use out of band metadata such as FDT data). This change adds the controller specification version to the check for whether to filter out the 1.8v selection. On older hardware, the 1.8v option is allowed to remain. On 3.0 or later it still requires the embedded-slot flag to remain. This is part of the fix for PR 241301 (eMMC not detected on Beaglebone). Changes to the sdhci_ti driver are also needed for a full fix. PR: 241301 r353652: Revert r351218 (by manu). While the changes in r351218 appear to be (and should be) correct, they lead to the eMMC on a Beaglebone failing to work in some situations. The TI sdhci hardware is kind of strange. The first device inherently supports 1.8v and 3.3v and the abililty to switch between them, and the other two devices must be set to 1.8v in the sdhci power control register to operate correctly, but doing so actually makes them run at 3.3v (unless an external level-shifter is present in the signal path). Even the 1.8v on the first device may actually be 3.3v (or any other value), depending on what voltage is fed to the VDDS1-VDDS7 power supply pins on the am335x chip. Another strange quirk is that the convention for am335x sdhci drivers in linux and uboot and the am335x boot ROM seems to be to set the voltage in the sdhci capabilities register to 3.0v even though the actual voltage is 3.3v. Why this is done is a complete mystery to me, but it seems to be required for correct operation. If we had complete modern support for the am335x chip we could get the actual voltages from the FDT data and the regulator framework. But our am335x code currently doesn't have any regulator framework support. Reverting to the prior code will get the popular Beaglebone boards working again. This is part of the fix for PR 241301, but also requires r353651 for a complete fix. PR: 241301 Discussed with: manu Approved by: re(kib) 2019-10-16T21:46:49Z Eric Joyner erj@FreeBSD.org 2019-10-16T21:46:49Z urn:sha1:6e69a11a2cc2db899d8448fc887e5a1a7321b747 This prevents a kernel panic when configuring EEE on X552 devices. PR: 240320 Approved by: re@ (gjb@) Sponsored by: Intel Corporation 2019-10-15T16:27:04Z Mark Johnston markj@FreeBSD.org 2019-10-15T16:27:04Z urn:sha1:598b25a307b4380f70121a63087bb5e499b933c3 Fix a couple of bugs around handling of PGA_WRITEABLE. Approved by: re (kib) 2019-10-15T16:05:55Z Michael Tuexen tuexen@FreeBSD.org 2019-10-15T16:05:55Z urn:sha1:2d45ee336530135fc56d491505f8be080a969ac4 Ensure that local variables are reset to their initial value when dealing with error cases in a loop over all remote addresses. This issue was found and reported by OSS_Fuzz in: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18080 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18086 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18121 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18163 MFS r353567: Fix mergeinfo for r353563. Approved by: re(gjb) 2019-10-15T14:45:33Z Mark Johnston markj@FreeBSD.org 2019-10-15T14:45:33Z urn:sha1:caa4f20dbe0525caf0f95a675b0cc1fcde8f4166 Fix handling of empty SCM_RIGHTS messages. Approved by: re (kib) 2019-10-15T06:19:33Z Toomas Soome tsoome@FreeBSD.org 2019-10-15T06:19:33Z urn:sha1:7f14d97e72d96b4cb23a666b4ea70737f23a1773 UEFI specification 2.7A, EFI_BLOCK_IO_PROTOCOL, page 566. The ioalign property does define the alignment of data buffer. If the alignment is required and our buffer is not aligned, or if the data buffer is not multiple of Blocksize, we need to use bounce buffer to perform the block IO. This is much like with BIOS version, except there the INT13 needs buffer to be located in low memory. MFS: r353501 MFC: r347195,350654-350656,351274,351630,351637,352421,352439,352443-352446,352451 Approved by: re (gjb)