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.
|r358174||kib||Feb. 20, 2020, 5:08 p.m.||Add more values for PCI capabilities, PCIe extended capabilities, and subclasses.
Taken from https://pcisig.com/sites/default/files/files/PCI_Code-ID_r_1_11__v24_Jan_2019.pdf Submitted by: Dmitry Luhtionov <firstname.lastname@example.org> MFC after: 1 weekViewVC
|r358173||mjg||Feb. 20, 2020, 4:58 p.m.||make sysent for r358172 ("vfs: add realpathat syscall")|
|r358172||mjg||Feb. 20, 2020, 4:58 p.m.||vfs: add realpathat syscall
realpath(3) is used a lot e.g., by clang and is a major source of getcwd and fstatat calls. This can be done more efficiently in the kernel. This works by performing a regular lookup while saving the name and found parent directory. If the terminal vnode is a directory we can resolve it using usual means. Otherwise we can use the name saved by lookup and resolve the parent. See the review for sample syscall counts. Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D23574ViewVC
|r358171||bapt||Feb. 20, 2020, 4:38 p.m.||Use OLD_LIBS instead of OLD_FILES so the user get a chance to keep them around if needed
Reported by: tijlViewVC
|r358170||pfg||Feb. 20, 2020, 3:52 p.m.||Revert r358153: it is causing unexpected issues with the build system.|
|r358169||tuexen||Feb. 20, 2020, 3:37 p.m.||Remove an unused timer type.
MFC after: 1 weekViewVC
|r358168||kib||Feb. 20, 2020, 3:34 p.m.||Do not read sigfastblock word on syscall entry.
On machines with SMAP, fueword executes two serializing instructions which can be seen in microbenchmarks. As a measure to restore microbenchmark numbers, only read the word on the attempt to deliver signal in ast(). If the word is set, signal is not delivered and word is kept, preventing interruption of interruptible sleeps by signals until userspace calls sigfastblock(UNBLOCK) which clears the word. This way, the spurious EINTR that userspace can see while in critical section is on first interruptible sleep, if a signal is pending, and on signal posting. It is believed that it is not important for rtld and lbithr critical sections. It might be visible for the application code e.g. for the callback of dl_iterate_phdr(3), but again the belief is that the non-compliance is acceptable. Most important is that the retry of the sleeping syscall does not interrupt unless additional signal is posted. For now I added the knob kern.sigfastblock_fetch_always to enable the word read on syscall entry to be able to diagnose possible issues due to spurious EINTR. While there, do some code restructuting to have all sigfastblock() handling located in kern_sig.c. Reviewed by: jeff Discussed with: mjg Tested by: pho Sponsored by: The FreeBSD Foundation Differential revision: https://reviews.freebsd.org/D23622ViewVC
|r358167||bz||Feb. 20, 2020, 10:56 a.m.||ip6_output: improve extension header handling
Move IPv6 source address checks from after extension header heandling to the top of the function. If we do not pass these checks there is no reason to do a lot of work upfront. Fold extension header preparations and length calculations together into a single branch and macro rather than doing them sequentially. Likewise move extension header concatination into a single branch block only doing it if we recorded any extension header length length. Reviewed by: melifaro (earlier version), markj, gallatin Sponsored by: Netflix (partially, originally) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D23740ViewVC
|r358166||bapt||Feb. 20, 2020, 9:33 a.m.||Update the UPDATING information now that ncurses shlib has been bumped|
|r358165||bapt||Feb. 20, 2020, 9:17 a.m.||Bump __FreeBSD_version after bumping ncurses shlib|
|r358164||bapt||Feb. 20, 2020, 9:12 a.m.||ncurses: bump shlib number to version 9
ABI has change in between ncurses 5 or 6. While theorically ncurses 6 is buildable with backward compatibility, I fail at building in a way where the application linked against the previous version of ncurses are rendering properly. Let's go on the new ABI which provides all the latest features. A compat12x package is cooking for backward compatibilityViewVC
|r358163||tsoome||Feb. 20, 2020, 9:02 a.m.||efi_register_handles() is missing NULL pointer check|
|r358162||tsoome||Feb. 20, 2020, 9 a.m.||insert_zfs() is missing NULL pointer check|
|r358160||tsoome||Feb. 20, 2020, 8:56 a.m.||efipart_inithandles() is missing NULL pointer check|
|r358159||tsoome||Feb. 20, 2020, 8:55 a.m.||connect_controllers() is missing NULL pointer check|