committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|a1c0442b||hselasky||May 4, 2022, 7:26 a.m.||xhci(4): Tweak USB port speed checks to allow newer super speed generations.
This allows setting the U1 and U2 port timeout values. MFC after: 1 week Sponsored by: NVIDIA Networkingcgit
|d730333c||hselasky||May 4, 2022, 7:26 a.m.||xhci(4): Properly define all basic USB port speeds.
MFC after: 1 week Sponsored by: NVIDIA Networkingcgit
|c4585b93||zec||May 4, 2022, 4:19 a.m.||tests: vnet tests started failing in CI, disable temporarily|
|9a3583bf||jkim||May 3, 2022, 7:12 p.m.||OpenSSL: Merge OpenSSL 1.1.1o|
|34252e89||jkim||May 3, 2022, 7:07 p.m.||OpenSSL: Merge OpenSSL 1.1.1o
Merge commit 'cf0ffd7607ed8f39829c6951a65a55fa1eb3aafe'cgit
|d461deea||zec||May 3, 2022, 5:27 p.m.||VNET: Revert "ifnet: make if_index global"
This reverts commit 91f44749c6feb50f39af8805dd803e860f0418f1. Devirtualization of V_if_index and V_ifindex_table was rushed into the tree lacking proper context, discussion, and declaration of intent, so I'm backing it out as harmful to VNET on the following grounds: 1) The change repurposed the decades-old and stable if_index KBI for new, unclear goals which were omitted from the commit note. 2) The change opened up a new resource exhaustion vector where any vnet could starve the system of ifnet indices, including vnet0. 3) To circumvent the newly introduced problem of separating ifnets belonging to different vnets from the globalized ifindex_table, the author introduced sysctl_ifcount() which does a linear traversal over the (potentially huge) global ifnet list just to return a simple upper bound on existing ifnet indices. 4) The change effectively led to nonuniform ifnet index allocation among vnets. 5) The commit note clearly stated that the patch changed the implicit if_index ABI contract where ifnet indices were assumed to be starting from one. The commit note also included a correct observation that holes in interface indices were always allowed, but failed to declare that the userland-observable ifindex tables could now include huge empty spans even under modest operating conditions. 6) The author had an earlier proposal in the works which did not affect per-vnet ifnet lists (D33265) but which he abandoned without providing the rationale behind his decision to do so, at the expense of sacrificing the vnet isolation contract and if_index ABI / KBI. Furthermore, the author agreed to back out his changes himself and to follow up with a proposal for a less intrusive alternative, but later silently declined to act. Therefore, I decided to resolve the status-quo by backing this out myself. This in no way precludes a future proposal aiming to mitigate ifnet-removal related system crashes or panics to be accepted, provided it would not unnecessarily compromise the goal of as strict as possible isolation between vnets. Obtained from: github.com/glebius/FreeBSD/commits/backout-ifindexcgit
|6c741ffb||zec||May 3, 2022, 5:11 p.m.||Revert "mbuf: do not restore dying interfaces"
This reverts commit 703e533da5e2e4743d38bbf4605fec041bc69976. Revert "ifnet/mbuf: provide KPI to serialize/restore m->m_pkthdr.rcvif" This reverts commit e1882428dcbbafd2814d7e17b977a8f686784b39. Obtained from: github.com/glebius/FreeBSD/commits/backout-ifindexcgit
|894c574e||zec||May 3, 2022, 5:11 p.m.||Revert "dummynet: use m_rcvif_serialize/restore when queueing packets"
This reverts commit 165746f4e4bf54c5902a103c2d4a3455e651c58f. Obtained from: github.com/glebius/FreeBSD/commits/backout-ifindexcgit
|0fa56369||zec||May 3, 2022, 5:11 p.m.||Revert "netisr: serialize/restore m_pkthdr.rcvif when queueing mbufs"
This reverts commit 6871de9363e559fef6765f0e49acc47f77544999. Obtained from: github.com/glebius/FreeBSD/commits/backout-ifindexcgit
|711524d9||zec||May 3, 2022, 5:11 p.m.||tests/dummynet: disable since mbuf pointer serialization KPI to be backed out
Obtained from: github.com/glebius/FreeBSD/commits/backout-ifindexcgit
|7ac164dc||manu||May 3, 2022, 4:15 p.m.||pkgbase: move devd's hyperv.conf to hyperv-tools package
This devd config file is useless without hyperv-tools, so we're moving it into the hyperv-tools package. pr#263691 PR: 263691 MFC after: 3 dayscgit
|09dd1adf||hselasky||May 3, 2022, 4:13 p.m.||xhci(4): Always add and evaluate the slot context.
Because the maximum number of endpoint contexts is stored there. Tested by: ehaupt@ PR: 262882 MFC after: 3 hours Sponsored by: NVIDIA Networkingcgit
|e276d281||hselasky||May 3, 2022, 4:13 p.m.||xhci(4): Only drop BULK and INTERRUPT endpoints to reset data toggle.
Only drop BULK and INTERRUPT endpoints, to reset the data toggle, because for other endpoint types this is not critical. Tested by: ehaupt@ PR: 262882 MFC after: 3 hours Sponsored by: NVIDIA Networkingcgit
|70910e4b||rmacklem||May 3, 2022, 2:22 p.m.||nfscl: Acquire a refcount on "cred" for mirrored pNFS RPCs
When the NFSv4.1/4.2 client is doing a pnfs mount to mirrored DS(s), asynchronous threads are used to do the RPCs against the DS(s) concurrently. If a DS is slow to reply, it is possible for the "cred" to be free'd before the asynchronous thread is done with it, causing a panic/crash. This patch fixes the problem by acquiring a refcount on the "cred" while it is being used by the asynchronous thread for a DS RPC. This bug was found during a recent IETF NFSv4 testing event. This bug only affects "pnfs" mounts to mirrored pNFS servers. MFC after: 2 weekscgit
|450b4ac2||manu||May 3, 2022, 2:02 p.m.||bsdinstall/script: umount before zpool export
When running zpool export first, boot/efi and dev is still mounted so zpool export fails. By running bsdinstall umount first the pool can be cleanly exported. Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D35114 Sponsored by: Beckhoff Automation GmbH & Co. KG MFC After: 3 dayscgit