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.
|c126924c||wosch||Feb. 5, 2022, 8:58 a.m.||update external URL|
|28e0b888||pho||Feb. 5, 2022, 8:51 a.m.||stress2: Fix compiler warnings|
|a6c20ddd||wosch||Feb. 5, 2022, 8:44 a.m.||switch from short to int for lookup table
This simplifies the code, less casting is needed.cgit
|6981ec8b||wosch||Feb. 5, 2022, 8:19 a.m.||update external URLs|
|7994ef3c||rscheff||Feb. 5, 2022, 12:07 a.m.||Revert "tcp: move ECN handling code to a common file"
This reverts commit 0c424c90eaa6602e07bca7836b1d178b91f2a88a.cgit
|dbc7364b||emaste||Feb. 5, 2022, 2:05 a.m.||elfctl: update man page example for 'no' prefix
Reported by: Mark Millard on freebsd-current@ Fixes: c763f99d11fd ("elfctl: prefix disable flags with "no"") MFC after: 1 week Sponsored by: The FreeBSD Foundationcgit
|18ed2ce7||asomers||Feb. 5, 2022, 1:44 a.m.||fusefs: fix the build without INVARIANTS after 00134a07898
MFC after: 2 weeks MFC with: 00134a07898fa807b8a1fcb2596f0e3644143f69 Reported by: secgit
|0c424c90||rscheff||Feb. 4, 2022, 9:54 p.m.||tcp: move ECN handling code to a common file
Reduce the burden to maintain correct and extensible ECN related code across multiple stacks and codepaths. Formally no functional change. Incidentially this establishes correct ECN operation in one instance. Reviewed By: rrs, #transport Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D34162cgit
|bca92be6||jhb||Feb. 4, 2022, 11:59 p.m.||Remove more quotes around Makefile .error/.warn/.info strings.|
|6bea696a||jhb||Feb. 4, 2022, 11:57 p.m.||linux_copyout_strings: Use PROC_PS_STRINGS().|
|ffe74ab7||jhb||Feb. 4, 2022, 11:57 p.m.||bsd.compat.mk: A few cosmetic fixes.|
|74fea8eb||jhb||Feb. 4, 2022, 11:38 p.m.||cxgbei: Rework parsing of pre-offload PDUs.
sbcut() returns mbufs in reverse order so is not suitable for reading data from the socket buffer. Instead, check for already-received data in the receive worker thread before passing offload PDUs up to the iSCSI layer. This uses soreceive() to read data from the socket and is also to use M_WAITOK since it now runs from a worker thread instead of an interrupt thread. Also, fix decoding of the data segment length for pre-offload PDUs. Reported by: Jithesh Arakkan @ Chelsio Fixes: a8c4147edcdc cxgbei: Parse all PDUs received prior to enabling offload mode. Sponsored by: Chelsio Communicationscgit
|00134a07||asomers||Feb. 4, 2022, 11:31 p.m.||fusefs: require FUSE_NO_OPENDIR_SUPPORT for NFS exporting
FUSE file systems that do not set FUSE_NO_OPENDIR_SUPPORT do not guarantee that d_off will be valid after closing and reopening a directory. That conflicts with NFS's statelessness, that results in unresolvable bugs when NFS reads large directories, if: * The file system _does_ change the d_off field for the last directory entry previously returned by VOP_READDIR, or * The file system deletes the last directory entry previously seen by NFS. Rather than doing a poor job of exporting such file systems, it's better just to refuse. Even though this is technically a breaking change, 13.0-RELEASE's NFS-FUSE support was bad enough that an MFC should be allowed. MFC after: 3 weeks. Reviewed by: rmacklem Differential Revision: https://reviews.freebsd.org/D33726cgit
|4a6526d8||asomers||Feb. 4, 2022, 11:30 p.m.||fusefs: optimize NFS readdir for FUSE_NO_OPENDIR_SUPPORT
In its lowest common denominator, FUSE does not require that a directory entry's d_off field is valid outside of the lifetime of the directory's FUSE file handle. But since NFS is stateless, it must reopen the directory on every call to VOP_READDIR. That means reading the directory all the way from the first entry. Not only does this create an O(n^2) condition for large directories, but it can also result in incorrect behavior if either: * The file system _does_ change the d_off field for the last directory entry previously seen by NFS, or * The file system deletes the last directory entry previously seen by NFS. Handily, for file systems that set FUSE_NO_OPENDIR_SUPPORT d_off is guaranteed to be valid for the lifetime of the directory entry, there is no need to read the directory from the start. MFC after: 3 weeks Reviewed by: rmacklemcgit
|d088dc76||asomers||Feb. 4, 2022, 11:30 p.m.||Fix NFS exports of FUSE file systems for big directories
The FUSE protocol does not require that a directory entry's d_off field outlive the lifetime of its directory's file handle. Since the NFS server must reopen the directory on every VOP_READDIR call, that means it can't pass uio->uio_offset down to the FUSE server. Instead, it must read the directory from 0 each time. It may need to issue multiple FUSE_READDIR operations until it finds the d_off field that it's looking for. That was the intention behind SVN r348209 and r297887, but a logic bug prevented subsequent FUSE_READDIR operations from ever being issued, rendering large directories incompletely browseable. MFC after: 3 weeks Reviewed by: rmacklemcgit