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.
|ae6bfd12||melifaro||Aug. 1, 2022, 10:02 a.m.||routing: refactor private KPI
* Make nhgrp_get_nhops() return const struct weightened_nhop to indicate that the list is immutable * Make nhgrp_get_group() return the actual group, instead of group+weight. MFC after: 2 weekscgit
|f28532a0||melifaro||Aug. 1, 2022, 9:20 a.m.||tests: fix unix_passfd_dgram:rights_creds_payload after be1f485d7d6b
The test was failing due to the assert on lack of MSG_TRUNC flag in the output flags of recvmsg(). The code passed MSG_TRUNC, along with sufficient-size buffer to hold the message to-be-received to the recvmsg(), and expected MSG_TRUNC to be returned as well. This is not exactly correct as a) MSG_TRUNC was not even a supported recvmsg() flag before be1f485d7d6b and b) it violates POSIX, as POSIX states it should be set only "If a message is too long to fit in the supplied buffers,". The test was working before as the kernel copied input flags to the output flags. be1f485d7d6b changed that behaviour to clear MSG_TRUNC if it was present on the input. Fix the test by checking POSIX-defined behaviour. Discussed with: glebiuscgit
|5c23343b||melifaro||Aug. 1, 2022, 8:55 a.m.||routing: convert remnants of DPRINTF to FIB_CTL_LOG().|
|800c6846||melifaro||Aug. 1, 2022, 8:52 a.m.||routing: add nhop(9) kpi.|
|29029b06||melifaro||Aug. 1, 2022, 7:41 a.m.||routing: remove info argument from add/change_route_nhop().
Currently, rt_addrinfo(info) serves as a main "transport" moving state between various functions inside the routing subsystem. As all of the fields are filled in directly by the customers, it is problematic to maintain consistency, resulting in repeated checks inside many functions. Additionally, there are multiple ways of specifying the same value (RTAX_IFP vs rti_ifp / rti_ifa) and so on. With the upcoming nhop(9) kpi it is possible to store all of the required state in the nexthops in the consistent fashion, reducing the need to use "info" in the KPI calls. Finally, rt_addrinfo structure format was derived from the rtsock wire format, which is different from other kernel routing users or netlink. This cleanup simplifies upcoming nhop(9) kpi and netlink introduction. Reviewed by: email@example.com Differential Revision: https://reviews.freebsd.org/D35972 MFC after: 2 weekscgit
|97ffaff8||melifaro||Aug. 1, 2022, 7:32 a.m.||net: constantify radix.c functions|
|2717e958||melifaro||Aug. 1, 2022, 7:26 a.m.||routing: move route expiration time to its nexthop|
|d22531d5||mckusick||Aug. 1, 2022, 5:07 a.m.||Identify each UFS/FFS superblock integrity check as a warning or fatal error.
Identify each of the superblock validation checks as either a warning or a fatal error. Any integrity check that can cause a system hang or crash is marked as fatal. Those that may simply lead to poor file layoutor other less good operating conditions are marked as warning. Normally both fatal and warning are treated as errors and prevent the superblock from being loaded. A new flag, UFS_NOWARNFAIL, is added. When passed to ffs_sbget() it will note warnings that it finds, but will still proceed with loading the superblock. Note that when UFS_NOWARNFAIL is used, it also includes UFS_NOHASHFAIL. No legitimate superblocks should fail as a result of these changes.cgit
|184e3118||mckusick||Aug. 1, 2022, 3:29 a.m.||Updates to UFS/FFS superblock integrity checks when reading a superblock.
Further updates based on analysis of the way the fields are used in the various filesystem macros defined in fs.h. Eliminate several checks for non-negative values where the fields are checked for specific values. Since these specific values are non-negative, if the value is a verified positive value then it cannot be negative and such a check is redundant and unnecessary. No legitimate superblocks should fail as a result of these changes.cgit
|0404b8c8||delphij||July 31, 2022, 10:16 p.m.||Deprecate minigzip(1) in preparation of removing it from base system.|
|3e40d2cc||mckusick||July 31, 2022, 2:49 p.m.||Fix for 548045b a too aggressive UFS superblock integrity check.
Reported by: Jenkinscgit
|321dc6ee||gbe||July 31, 2022, 2:38 p.m.||find.1: Fix mandoc warnings and mention a useful manpage
- new sentence, new line - unknown AT&T UNIX version: At v7 - no blank before trailing delimiter - reference the ASCII(8) manual page MFC after: 5 dayscgit
|b131efe3||gbe||July 31, 2022, 2:23 p.m.||sh.1: Fix a mandoc warning
- new sentence, new line MFC after: 3 dayscgit
|2bf1b998||gbe||July 31, 2022, 10:27 a.m.||uhsoctl.1: Fix the man page date
- STYLE: normalizing date format to: August 12, 2009 MFC after: 3 dayscgit
|98b610b5||gbe||July 31, 2022, 10:14 a.m.||uefi(8): Fix a typo in a source code comment
- s/intrrupt/interrupt/ MFC after: 3 dayscgit