src/usr.sbin, branch releng/11.3

Fix multiple vulnerabilities in unbound.

2020-07-08T20:20:59Z

Approved by: so Security: FreeBSD-SA-20:19.unbound Security: CVE-2020-12662 Security: CVE-2020-12663

Fix multiple denial of service in ntpd.

2020-03-19T16:52:41Z

Approved by: so Security: FreeBSD-SA-20:09.ntp

Fix insufficient validation of guest-supplied data (e1000 device).

2019-08-06T17:13:17Z

Approved by: so Security: FreeBSD-SA-19:21.bhyve Security: CVE-2019-5609

Fix byhve out-of-bounds read in XHCI device.

2019-07-24T12:56:06Z

Approved by: so Security: FreeBSD-SA-19:16.bhyve Security: CVE-2019-5604

MFC r349376: Fix strsep_quote() on strings without quotes.

2019-06-27T14:26:57Z

For strings without quotes and escapes dstptr and srcptr are equal, so zeroing *dstptr before checking *srcptr is not a good idea. In practice it means that in -maproot=65534:65533 everything after the colon is lost. The problem was there since r293305, but before r346976 it was covered by improper strsep_quote() usage. PR: 238725 Approved by: re (gjb)

MFC 347033:

2019-05-29T23:11:07Z

Increase the VirtIO segment count to support modern Windows guests. The Windows virtio driver ignores the advertized seg_max field and assumes the host can accept up to 67 segments in indirect descriptors, triggering an assert in the bhyve process. This brings back r282922 but with a couple of changes: - It raises the block interface segment limit to 128 instead of 67. - Linux's virtio driver assumes that the segment limit is no larger than the ring size. To avoid breaking Linux guests, raise the VirtIO ring size to 128, and cap the VirtIO segment limit at ring size - 2 (effectively 126). Approved by: re (gjb)

MFC 345158: Fix uart emulation bug

2019-05-29T20:45:31Z

THRE is always asserted in LSR reads, so REG_IER writes that raise IER_ETXRDY must also set thre_int_pending. Approved by: re (gjb)

MFC: r346717: Make bhyve SMBIOS table topology aware

2019-05-25T10:17:03Z

When the CPU Topology was added to bhyve in r332298 the SMBIOS table was missed, this table passes topology information to the system and was still using the old concept of each vCPU is a socket with 1 core and 1 thread. This code did not even try to use the old sysctl information to adjust this data. Correct that by building a proper SMBios table, mapping the > 254 cases to 0 per the SMBios 2.6 specification that is claimed by the structure. Approved by: re (kib)

MFC: r332298,333712,334199,334216,334219 bhyve cpu topology

2019-05-23T21:23:18Z

Approved by: re (gjb), bde/phk (mentor, implicit)

MFC: r347960: bhyve virtio needs barriers

2019-05-23T18:58:06Z

Under certain tight race conditions, we found that the lack of a memory barrier in bhyve's virtio handling causes it to miss a NO_NOTIFY state transition on block devices, resulting in guest stall. The investigation is recorded in OS-7613. As part of the examination into bhyve's use of barriers, one other section was found to be problematic, but only on non-x86 ISAs with less strict memory ordering. That was addressed in this patch as well, although it was not at all a problem on x86. PR: 231117 Submitted by: Patrick Mooney Reviewed by: jhb, kib, rgrimes Approved by: re (gjb), jhb Differential Revision: https://reviews.freebsd.org/D19501