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.
|3b57d80c||asomers||May 3, 2021, 3:55 p.m.||daemon: add some basic tests|
|7818653f||trasz||May 3, 2021, 2:20 p.m.||cam: fix integer overflow during inquiry
From my understanding this could happen with iSCSI LUNs with unusually long names. The bug would make CAM fail to retrieve the full inquiry data. Instead of bumping the size of the local variable, just use a macro. Reviewed By: imp, mav Sponsored by: NetApp, Inc. Sponsored by: Klara, Inc. X-NetApp-PR: #50 Differential Revision: https://reviews.freebsd.org/D29991cgit
|8f156243||kib||May 3, 2021, 11:38 a.m.||Add Apollo Lake SIO/LPSS UARTs PCI IDs
Add PCI IDs for Intel Apollo Lake Series HSUARTs: # pciconf -ll drv selector class rev hdr vendor device subven subdev uart0@pci0:0:24:0: 118000 0b 00 8086 5abc 8086 7270 uart1@pci0:0:24:1: 118000 0b 00 8086 5abe 8086 7270 uart2@pci0:0:24:2: 118000 0b 00 8086 5ac0 8086 7270 uart3@pci0:0:24:3: 118000 0b 00 8086 5aee 8086 7270 NB (Intel Document Number 336256-004US): 1. The E3900 and A3900 Series Processors support four LPSS_UART ports, while the N- and J- Series Processors support only LPSS_UART [2:1] ports. 2. The LPSS_UART1 port is dedicated for discrete Global Navigation Satellite System (GNSS). This port can be used for generic UART functionality if GNSS is not used. 3. The LPSS_UART2 port is dedicated for host OS debug. 4. The LPSS_UART0 and LPSS_UART3 ports are for generic UART functionality. 5. Only UART [1:0] ports support DMA. PR: 255556 Submitted by: Jose Luis Duran <email@example.com> MFC after: 1 weekcgit
|5b8b6b26||kib||May 3, 2021, 11:38 a.m.||uart_bus_pci.c: Style|
|0ea8a7f3||kib||May 3, 2021, 11:38 a.m.||ifconfig: Minor documentation fix|
|0ec20519||andrew||May 3, 2021, 8:36 a.m.||Also enable IPIs on 32-bit arm
This was missed in 2420f6a Reported by: tuexen, impcgit
|5c4fe2ac||donner||May 3, 2021, 10:27 a.m.||service/ipfw: Silence warning on restart|
|cff133b0||pho||May 3, 2021, 7:08 a.m.||stress2: Added a regression test|
|a7d46ad0||pho||May 3, 2021, 7:05 a.m.||stress2: Added a syzkaller reproducer|
|573bd33a||pho||May 3, 2021, 6:45 a.m.||stress2: Fix a typo.|
|8b3d0f64||tuexen||May 3, 2021, 12:50 a.m.||sctp: improve address list scanning
If the alternate address has to be removed, force the stack to find a new one, if it is still needed. MFC after: 3 dayscgit
|a89481d3||tuexen||May 3, 2021, 12:20 a.m.||sctp: improve restart handling
This fixes in particular a possible use after free bug reported Anatoly Korniltsev and Taylor Brandstetter for the userland stack. MFC after: 3 dayscgit
|655c200c||mav||May 3, 2021, 12:07 a.m.||Fix build after 5f2e1835054ee84f2e68ebc890d92716a91775b7.|
|2760658b||mav||May 2, 2021, 11:45 p.m.||Improve UMA cache reclamation.
When estimating working set size, measure only allocation batches, not free batches. Allocation and free patterns can be very different. For example, ZFS on vm_lowmem event can free to UMA few gigabytes of memory in one call, but it does not mean it will request the same amount back that fast too, in fact it won't. Update working set size on every reclamation call, shrinking caches faster under pressure. Lack of this caused repeating vm_lowmem events squeezing more and more memory out of real consumers only to make it stuck in UMA caches. I saw ZFS drop ARC size in half before previous algorithm after periodic WSS update decided to reclaim UMA caches. Introduce voluntary reclamation of UMA caches not used for a long time. For each zdom track longterm minimal cache size watermark, freeing some unused items every UMA_TIMEOUT after first 15 minutes without cache misses. Freed memory can get better use by other consumers. For example, ZFS won't grow its ARC unless it see free memory, since it does not know it is not really used. And even if memory is not really needed, periodic free during inactivity periods should reduce its fragmentation. Reviewed by: markj, jeff (previous version) MFC after: 2 weeks Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D29790cgit
|5f2e1835||tuexen||May 2, 2021, 8:41 p.m.||sctp: improve error handling in INIT/INIT-ACK processing
When processing INIT and INIT-ACK information, also during COOKIE processing, delete the current association, when it would end up in an inconsistent state. MFC after: 3 dayscgit