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.
|r353696||cem||Oct. 17, 2019, 8:25 p.m.||debugnet(4): Add optional full-duplex mode|
|r353695||glebius||Oct. 17, 2019, 8:18 p.m.||Revert two parts of r353292 that enter epoch when processing vlan capabilities.
It could be that entering epoch isn't necessary here, but better take a conservative approach. Submitted by: kpViewVC
|r353694||cem||Oct. 17, 2019, 8:10 p.m.||debugnet(4): Infer non-server connection parameters
Loosen requirements for connecting to debugnet-type servers. Only require a destination address; the rest can theoretically be inferred from the routing table. Relax corresponding constraints in netdump(4) and move ifp validation to debugnet connection time. Submitted by: John Reimer <john.reimer AT emc.com> (earlier version) Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D21482ViewVC
|r353693||cem||Oct. 17, 2019, 7:53 p.m.||acpica: Fix for the fix, unfortunately
Follow-up to incomplete pedantic change in r353691 by actually fixing the default implementation to match the interface type. Mea culpa. X-MFC-With: r353691, r339754ViewVC
|r353692||cem||Oct. 17, 2019, 7:49 p.m.||Add ddb(4) 'netdump' command to netdump a core without preconfiguration
Add a 'X -s <server> -c <client> [-g <gateway>] -i <interface>' subroutine to the generic debugnet code. The imagined use is both netdump, shown here, and NetGDB (vaporware). It uses the ddb(4) lexer, with some new extensions, to parse out IPv4 addresses. 'Netdump' uses the generic debugnet routine to load a configuration and start a dump, without any netdump configuration prior to panic. Loosely derived from work by: John Reimer <john.reimer AT emc.com> Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D21460ViewVC
|r353691||cem||Oct. 17, 2019, 6:45 p.m.||acpica: Match ID_PROBE default implementation to interface
After r339754, the additional interface parameter was accidentally left out of the default acpi_generic_id_probe implementation. Apparently this does not cause any real problems, so this fix is mostly stylistic. No functional change intended. X-MFC-With: r339754ViewVC
|r353690||cem||Oct. 17, 2019, 6:29 p.m.||Add a very limited DDB dumpon(8)-alike to MI dumper code
This allows ddb(4) commands to construct a static dumperinfo during panic/debug and invoke doadump(false) using the provided dumper configuration (always inserted first in the list). The intended usecase is a ddb(4)-time netdump(4) command. Reviewed by: markj (earlier version) Differential Revision: https://reviews.freebsd.org/D21448ViewVC
|r353689||cem||Oct. 17, 2019, 5:48 p.m.||debugnet: Respond to broadcast ARP requests
The in-tree netdump code has always ignored non-directed ARP requests, and that seems to work most of the time for netdump. In my work and testing on NetGDB, it seems like sometimes the remote FreeBSD conversant (the non-panic system) will send broadcast-destination ARP requests to the debugnet kernel; without this change, those are dropped and the remote will see EHOSTDOWN "Host is down" errors from the userspace interface of the network stack. Discussed with: markjViewVC
|r353688||cem||Oct. 17, 2019, 5:19 p.m.||debugnet(4): Check hardware-validated UDP checksums|
|r353687||glebius||Oct. 17, 2019, 5:02 p.m.||Quickly fix up r353683: enter the epoch before calling into netisr_dispatch().|
|r353686||emaste||Oct. 17, 2019, 4:38 p.m.||Update Conrad Meyer's email
cem is now a committer Approved by: cemViewVC
|r353685||cem||Oct. 17, 2019, 4:23 p.m.||Split out a more generic debugnet(4) from netdump(4)
Debugnet is a simplistic and specialized panic- or debug-time reliable datagram transport. It can drive a single connection at a time and is currently unidirectional (debug/panic machine transmit to remote server only). It is mostly a verbatim code lift from netdump(4). Netdump(4) remains the only consumer (until the rest of this patch series lands). The INET-specific logic has been extracted somewhat more thoroughly than previously in netdump(4), into debugnet_inet.c. UDP-layer logic and up, as much as possible as is protocol-independent, remains in debugnet.c. The separation is not perfect and future improvement is welcome. Supporting INET6 is a long-term goal. Much of the diff is "gratuitous" renaming from 'netdump_' or 'nd_' to 'debugnet_' or 'dn_' -- sorry. I thought keeping the netdump name on the generic module would be more confusing than the refactoring. The only functional change here is the mbuf allocation / tracking. Instead of initiating solely on netdump-configured interface(s) at dumpon(8) configuration time, we watch for any debugnet-enabled NIC for link activation and query it for mbuf parameters at that time. If they exceed the existing high-water mark allocation, we re-allocate and track the new high-water mark. Otherwise, we leave the pre-panic mbuf allocation alone. In a future patch in this series, this will allow initiating netdump from panic ddb(4) without pre-panic configuration. No other functional change intended. Reviewed by: markj (earlier version) Some discussion with: emaste, jhb Objection from: marius Differential Revision: https://reviews.freebsd.org/D21421ViewVC
|r353683||glebius||Oct. 17, 2019, 4:02 p.m.||igmp_v1v2_queue_report() doesn't require epoch.|
|r353682||emaste||Oct. 17, 2019, 2:58 p.m.||snd_hda: style(9) whitespace fixup
PR: 241299 Submitted by: Neel ChauhanViewVC
|r353681||kib||Oct. 17, 2019, 1:49 p.m.||swapon_check_swzone(): use already calculated static variables.|