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.
|r344041||ngie||Feb. 12, 2019, 3:32 a.m.||Bump `__FreeBSD_version__` for r343891
This will allow upstream consumers, e.g., capsicum-test and third-party packages (via ports(7)), to test for a specific `__FreeBSD_version__` and expect `renameat(2)` to be functional. PR: 222258 Approved by: emaste (mentor) Reviewed by: emaste MFC with: r343891 Differential Revision: https://reviews.freebsd.org/D19154ViewVC
|r344036||kevlo||Feb. 12, 2019, 2:55 a.m.||Remove entry for Intenso product.|
|r344035||kevlo||Feb. 12, 2019, 2:48 a.m.||Remove duplicate vendor id in r334650. Intenso doesn't have a USB VID.|
|r344034||kevans||Feb. 12, 2019, 2:16 a.m.||libbe(3): Belatedly note the BE_DESTROY_ORIGIN option added in r343977
|r344025||pkelsey||Feb. 11, 2019, 10:58 p.m.||Fix the fix added in r343287 for spurious HFSC bandwidth check errors
The logic added in r343287 to avoid false-positive sum-of-child-bandwidth check errors for HFSC queues has a bug in it that causes the upperlimit service curve of an HFSC queue to be pulled down to its parent's linkshare service curve if it happens to be above it. Upon further inspection/reflection, this generic sum-of-child-bandwidths check does not need to be fixed for HFSC - it needs to be skipped. For HFSC, the equivalent check is to ensure the sum of child linkshare service curves are at or below the parent's linkshare service curve, and this check is already being performed by eval_pfqueue_hfsc(). This commit reverts the affected parts of r343287 and adds new logic to skip the generic sum-of-child-bandwidths check for HFSC. MFC after: 1 day Sponsored by: RG Nets Differential Revision: https://reviews.freebsd.org/D19124ViewVC
|r344024||dab||Feb. 11, 2019, 10:09 p.m.||CID 1009492: Logically dead code in sys/cam/scsi/scsi_xpt.c
In `probedone()`, for the `PROBE_REPORT_LUNS` case, all paths that fall to the bottom of the case set `lp` to `NULL`, so the test for a non-NULL value of `lp` and call to `free()` if true is dead code as the test can never be true. Fix by eliminating the whole if statement. To guard against a possible future change that accidentally violates this assumption, use a `KASSERT()` to catch if `lp` is non-NULL. Reviewed by: cem MFC after: 1 week Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D19109ViewVC
|r344023||brooks||Feb. 11, 2019, 9:31 p.m.||mdmfs: Fix many bugs in automatic md(4) creation.
This code allocated a correctly sized buffer, read past the end of the source buffer, writing off the end of the target buffer, and then writing a '\0' terminator past the end of the target buffer (in the wrong place). It then leaked the buffer. Switch to a statically sized buffer on the stack and update the source pointer and length before use so the correct things are copied. Fix a logic error in the checks that the format of the line is as expected and move on out of an assert. Remove an unneeded close(). fclose() closes the descriptor. Found with: CheriABI Obtained from: CheriBSD Reviewed by: kib, jhb, markj Differential Revision: https://reviews.freebsd.org/D19122ViewVC
|r344022||jhb||Feb. 11, 2019, 8:47 p.m.||Enable PCI BAR reallocation by default.
When pci_realloc_bars was first added, the intention was to eventually enable it by default, but it was left disabled to preserve existing behavior. The setting is pretty conservative in that it does not attempt to allocate resources for BARs that the BIOS/firmware leaves disabled. It only attempts to reallocate resources for a BAR that the firmware programmed during boot but that conflicts with another resource during the kernel's device scan. PR 221350 is an example of a machine that this knob fixes. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D18965ViewVC
|r344021||trasz||Feb. 11, 2019, 8:46 p.m.||Add explanation of branches to the ports(7) man page.|
|r344018||ae||Feb. 11, 2019, 6:10 p.m.||Remove `set' field from state structure and use set from parent rule.
Initially it was introduced because parent rule pointer could be freed, and rule's information could become inaccessible. In r341471 this was changed. And now we don't need this information, and also it can become stale. E.g. rule can be moved from one set to another. This can lead to parent's set and state's set will not match. In this case it is possible that static rule will be freed, but dynamic state will not. This can happen when `ipfw delete set N` command is used to delete rules, that were moved to another set. To fix the problem we will use the set number from parent rule. Obtained from: Yandex LLC MFC after: 1 week Sponsored by: Yandex LLCViewVC
|r344015||cracauer||Feb. 11, 2019, 4:31 p.m.||Bump .Dd for today's edit.
Thank you Enji CooperViewVC
|r344013||cracauer||Feb. 11, 2019, 3:51 p.m.||Clarify NFSv4 /etc/exports semantics, with working example.
The existing wording has been confusing users for years.ViewVC
|r344012||tuexen||Feb. 11, 2019, 3:38 p.m.||Fix flags used when compiling kern_kcov.c and subr_coverage.c.|
|r344003||ganbold||Feb. 11, 2019, 2:31 p.m.||Add sensors support for AXP803/AXP813. Sensor values such as|
|r343998||gonzo||Feb. 11, 2019, 7:42 a.m.||Fix off-by-one error in BERI virtio driver
The hardcoded ident is exactly 20 bytes long but sprintf adds terminating zero, so there is one byte written out of array bounds.As a fix use strncpy it appends \0 only if space allows and its behavior matches virtio spec: When VIRTIO_BLK_T_GET_ID is issued, the device identifier, up to 20 bytes, is written to the buffer. The identifier should be interpreted as an ascii string. It is terminated with \0, unless it is exactly 20 bytes long. PR: 202298 Reviewed by: br MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D18852ViewVC