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.
|a305b20e||allanjude||July 18, 2022, 10:06 p.m.||ddb: tag core commands with DB_CMD_MEMSAFE|
|c84c5e00||allanjude||July 18, 2022, 10:06 p.m.||ddb: annotate some commands with DB_CMD_MEMSAFE|
|bb61cba7||allanjude||July 18, 2022, 10:06 p.m.||ddb: add the DB_CMD_MEMSAFE flag for commands
This flag value can be used to indicate if a command has the property of being "memory safe". In this instance, memory safe means that the command does not allow/enable reads or writes of arbitrary memory, regardless of the arguments passed to it. For example, 'backtrace' is considered a memory-safe command since its output is deterministic, while 'show vnode' is not, since it requires a memory address as an argument and will print the contents beginning at that location. Apply the flag to the "show all" command macros. It is expected that commands added to this table will always exhibit this property. Reviewed by: markj Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D35581cgit
|3ca4a339||vangyzen||July 18, 2022, 9:05 p.m.||bge: tell debugnet there are 2 rx rings, not 1,024
debugnet provides the network stack for netgdb and netdump. Since it must operate under panic/debugger conditions and can't rely on dynamic memory allocation, it preallocates mbufs during boot or network configuration. At that time, it does not yet know which interface will be used for debugging, so it does not know the required size and quantity of mbufs to allocate. It takes the worst-case approach by calculating its requirements from the largest MTU and largest number of receive queues across all interfaces that support debugnet. Unfortunately, the bge NIC driver told debugnet that it supports 1,024 receive queues. It actually supports only 2 queues (with 1,024 slots, thus the error). This greatly exaggerated debugnet's preallocation, so with an MTU of 9000 on any interface, it allocated 600 MB of memory. A tiny fraction of this memory would be used if netgdb or netdump were invoked; the rest is completely wasted. Reviewed by: markj, rlibby MFC after: 1 week Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D35845cgit
|bd980ca8||markj||July 18, 2022, 7:52 p.m.||sched_ule: Ensure we hold the thread lock when modifying td_flags
The load balancer may force a running thread to reschedule and pick a new CPU. To do this it sets some flags in the thread running on a loaded CPU. But the code assumed that a running thread's lock is the same as that of the corresponding runqueue, and there are small windows where this is not true. In this case, we can end up with non-atomic modifications to td_flags. Since this load balancing is best-effort, simply give up if the thread's lock doesn't match; in this case the thread is about to enter the scheduler anyway. Reviewed by: kib Reported by: glebius Fixes: e745d729be60 ("sched_ule(4): Improve long-term load balancer.") MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D35821cgit
|f5ad538d||mjg||July 18, 2022, 6:43 p.m.||i386: fix pmap_trm_arena_last atomic load type
Sponsored by: Rubicon Communications, LLC ("Netgate")cgit
|df777aeb||emaste||July 18, 2022, 5:24 p.m.||vtfontcvt: correct usage
Commit e7fd9688ea97 changed vtfontcvt's command line parsing, but did not correctly update the usage (it omitted the new -o flag). Fixes: e7fd9688ea97 ("Move font related data structured to...") MFC after: 1 week Sponsored by: The FreeBSD Foundationcgit
|939f0b63||kd||July 18, 2022, 2:27 p.m.||Implement shared page address randomization
It used to be mapped at the top of the UVA. If the randomization is enabled any address above .data section will be randomly chosen and a guard page will be inserted in the shared page default location. The shared page is now mapped in exec_map_stack, instead of exec_new_vmspace. The latter function is called before image activator has a chance to parse ASLR related flags. The KERN_PROC_VM_LAYOUT sysctl was extended to provide shared page address. The feature is enabled by default for 64 bit applications on all architectures. It can be toggled kern.elf64.aslr.shared_page sysctl. Approved by: mw(mentor) Sponsored by: Stormshield Obtained from: Semihalf Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D35349cgit
|361971fb||kd||July 18, 2022, 2:27 p.m.||Rework how shared page related data is stored
Store the shared page address in struct vmspace. Also instead of storing absolute addresses of various shared page segments save their offsets with respect to the shared page address. This will be more useful when the shared page address is randomized. Approved by: mw(mentor) Sponsored by: Stormshield Obtained from: Semihalf Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D35393cgit
|f6ac79fb||kd||July 18, 2022, 2:27 p.m.||Introduce the PROC_SIGCODE() macro
Use a getter macro instead of fetching the sigcode address directly from a sysent of a given process. It assumes that the sigcode is stored in the shared page, which is true in all cases, except for a.out binaries. This will be later useful when the shared page address randomization is introduced. No functional change intended. Approved by: mw(mentor) Sponsored by: Stormshield Obtained from: Semihalf Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D35392cgit
|ddd9004e||markj||July 18, 2022, 1:45 p.m.||Bump __FreeBSD_version after the removal of OBJT_DEFAULT
Out-of-tree modules which allocate an object of type OBJT_DEFAULT need to be recompiled. No other changes are required, however.cgit
|a11f080e||karels||July 18, 2022, 1:02 p.m.||ofed/infiniband: fix ifdefs for new INET changes, fixing LINT-NOIP
Some of the ofed/infiniband code has INET and INET6 address handling code without using ifdefs. This failed with a recent change to INET, in which IN_LOOPBACK() started using a VNET variable, and which is not present if INET is not configured. Add #ifdef INET, and INET6 for good measure, in cma_loopback_addr(), along with inclusion of the options headers in ib_cma.c. Reviewed by: hselasky rgrimes bz Differential Revision: https://reviews.freebsd.org/D35835 (cherry picked from commit 752b7632776237f9c071783acdd1136ebf5f287d)cgit
|b1e81e6d||emaste||July 18, 2022, 12:55 p.m.||blacklistd: Handle 0 sized messages|
|fe88072d||bz||July 18, 2022, 11:51 a.m.||arm64, qoriq_therm: fix handling sites on version 1 and 2
For version 2 extend the TMUV2_TMSAR() write loop over all site_ids registered for a particular SoC and actually use the site_id rather than always just the first  (which for the LX2080 would be a problem given there is no site0). Later, while version 2 adds the SITEs to enable to TMSR in bits 0..<n>, version 1 (e.g., LS1028, LS1046, LS1088) add MSITEs to TMR bits 16..31 or rather 15..0(16-<n>). Adjust the loops to only enable the site_ids listed for the particular SoC for monitoring. This now also deals with sparse site_ids (not starting at 0, or not being contiguous). MFC after: 1 week Sponsored by: Traverse Technologies (providing Ten64 HW for testing) Reviewed by: mmel Differential Revision: https://reviews.freebsd.org/D35764cgit
|39445330||bz||July 18, 2022, 11:47 a.m.||arm64, qoriq_therm: configure the number of sites base don SoC
Configure the number of sites (sensors) based on SoC. This avoids timeouts reading non-existent sensors. The changes are based on mmel's initial work at: https://github.com/strejda/freebsd/commit/914e3f0098b090cb5c1492b0d24992012c5c553b MFC after: 1 week Sponsored by: Traverse Technologies (providing Ten64 HW for testing) Reviewed by: mmel Differential Revision: https://reviews.freebsd.org/D35759cgit