committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r366863||br||Oct. 19, 2020, 9:27 p.m.||Add IOMMU_BUSWIDE ahci quirk.
Some controllers use PCI function 1 as the requester ID for DMA transfers, but the controllers are not PCI multifunction. Set the iommu buswide flag for them. This should instruct an IOMMU driver to use the same translation rule for all the devices and functions of a bus. This was discovered on the ARM Neoverse N1 System Development Platform (ARM N1SDP). Bug reference: https://bugzilla.kernel.org/show_bug.cgi?id=42679 Reported by: andrew Reviewed by: kib, mav Sponsored by: Innovate DSbD Differential Revision: https://reviews.freebsd.org/D26857ViewVC
|r366862||np||Oct. 19, 2020, 9:11 p.m.||cxgbe(4): Updates to the drop features from r366532.
MFC after: 1 week Sponsored by: Chelsio CommunicationsViewVC
|r366861||emaste||Oct. 19, 2020, 8:43 p.m.||build vmware modules on arm64
pvscsi and vmxnet3 build and work. Exclude vmci for now as it contains x86-specific assembly. Reported by: Vincent Milum Jr MFC after: 2 weeks Sponsored by: The FreeBSD FoundationViewVC
|r366857||cy||Oct. 19, 2020, 8:37 p.m.||Destroy cloned interfaces at netif stop, netif restart and shutdown.
This is especially important during shutdown because a child interface of lagg with WOL enabled will not enable WOL at interface shutdown and thus no WOL to wake up the device (and machine). PR: 158734, 109980 Reported by: Antonio Huete Jimenez <tuxillo at quantumachine.net> Marat N.Afanasyev <marat at zealot.ksu.ru> reviewed by: kp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D26797ViewVC
|r366855||trasz||Oct. 19, 2020, 8:26 p.m.||Fix fallout from r366811.|
|r366854||jhb||Oct. 19, 2020, 8:08 p.m.||Re-enable receive flow control for TOE TLS sockets.
Flow control was disabled during initial TOE TLS development to workaround a hang (and to match the Linux TOE TLS support for T6). The rest of the TOE TLS code maintained credits as if flow control was enabled which was inherited from before the workaround was added with the exception that the receive window was allowed to go negative. This negative receive window handling (rcv_over) was because I hadn't realized the full implications of disabling flow control. To clean this up, re-enable flow control on TOE TLS sockets. The existing TPF_FORCE_CREDITS workaround is sufficient for the original hang. Now that flow control is enabled, remove the rcv_over workaround and instead assert that the receive window never goes negative matching plain TCP TOE sockets. Reviewed by: np MFC after: 2 weeks Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D26799ViewVC
|r366853||np||Oct. 19, 2020, 8:08 p.m.||cxgbe(4): Fix page fault in t4_get_lb_stats with 2 port T5 cards.
PR: 250449 Reported by: freqlabs@ MFC after: 1 week Sponsored by: Chelsio CommunicationsViewVC
|r366852||jhb||Oct. 19, 2020, 8:04 p.m.||Fix a couple of bugs for asym crypto introduced in r359374.
- Check for null pointers in the crypto_drivers array when checking for empty slots in crypto_select_kdriver(). - Handle the case where crypto_kdone() is invoked on a request where krq_cap is NULL due to not finding a matching driver. Reviewed by: markj Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D26811ViewVC
|r366851||arichardson||Oct. 19, 2020, 7:51 p.m.||Enable SUBDIR_PARALLEL for lib/googletest|
|r366850||arichardson||Oct. 19, 2020, 7:50 p.m.||Major improvement to build parallelism for googletest internal tests
Currently the googletest internal tests build after the matching library. However, each of these is serialized at the top level makefile. Additionally some of the tests (e.g. the gmock-matches-test) take up to 90 seconds to build with clang -O2. Having to wait for this test to complete before continuing to the next directory seriously slows down the parllelism of a -j32 build. Before this change running `make -C lib/googletest -j32 -s` in buildenv took 202 seconds, now it's 153 due to improved parallelism. Reviewed By: emaste (no objection) Differential Revision: https://reviews.freebsd.org/D26748ViewVC
|r366849||kib||Oct. 19, 2020, 7:23 p.m.||nullfs: ensure correct lock is taken after bypass.
If lower VOP relocked the lower vnode, it is possible that nullfs vnode was reclaimed meantime. In this case nullfs vnode no longer shares lock with lower vnode, which breaks locking protocol. Check for the condition and acquire nullfs vnode lock if detected. Reported and tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 1 weekViewVC
|r366848||kib||Oct. 19, 2020, 7:20 p.m.||vgonel(): avoid recursing into VOP_INACTIVE().
It is a common pattern for filesystems' VOP_INACTIVE() implementation to forcibly reclaim the vnode when its state is final. For instance, UFS vnode with zero link count is removed, and since it is inactivated, the last open reference on it is dropped. On the other hand, vnode might get spurious usecount reference for many reasons. If the spurious reference exists while vgonel() checks for active state of the vnode, it would recurse into VOP_INACTIVE(). Fix it by checking and not doing inactivation when vgone() was called from inactive VOP. Reported and tested by: pho Discussed with: mjg Sponsored by: The FreeBSD Foundation MFC after: 1 weekViewVC
|r366847||emaste||Oct. 19, 2020, 6:54 p.m.||uma: fix KTR message after r366840
Reported by: bz Sponsored by: The FreeBSD FoundationViewVC
|r366846||mjg||Oct. 19, 2020, 6:51 p.m.||cache: promote negative entries based on more than one hit
During tinderbox and similar workloads negative entries get at least one hit before they get evicted. In the current scheme this avoidably promotes them. Be conservative and stick to 2 hits for now.ViewVC
|r366845||jhb||Oct. 19, 2020, 6:24 p.m.||Check TF_TOE not the tod pointer to determine if TOE is active.
The TF_TOE flag is the check used in the rest of the network stack to determine if TOE is active on a socket. There is at least one path in the cxgbe(4) TOE driver that can leave the tod pointer non-NULL on a socket not using TOE. Reported by: Sony Arpita Das <firstname.lastname@example.org> Reviewed by: np Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D26803ViewVC