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.
|333ba164||tuexen||July 29, 2019, 8:50 a.m.||* Improve input validation of sysctl parameters for DCTPC.|
|8de2d8c0||mav||July 29, 2019, 3:28 a.m.||Add some new fields and bits from NVMe 1.4.|
|adf495e2||noreply||July 29, 2019, 1:15 a.m.||Fix channel programs on s390x
When adapting the original sources for s390x the JMP_BUF_CNT was mistakenly halved due to an incorrect assumption of the size of a unsigned long. They are 8 bytes for the s390x architecture. Increase JMP_BUF_CNT accordingly. Authored-by: Don Brady <firstname.lastname@example.org> Reviewed-by: Brian Behlendorf <email@example.com> Reported-by: Colin Ian King <canonical.com> Tested-by: Colin Ian King <canonical.com> Signed-off-by: Brian Behlendorf <firstname.lastname@example.org> Closes #8992 Closes #9080cgit
|453bb479||behlendorf1||July 29, 2019, 1:13 a.m.||Race between zfs-share and zfs-mount services
When a system boots the zfs-mount.service and the zfs-share.service can start simultaneously. What may be unclear is that sharing a filesystem will first mount the filesystem if it's not already mounted. This means that both service can race to mount the same fileystem. This race can result in a SEGFAULT or EBUSY conditions. This change explicitly defines the start ordering between the two services such that the zfs-mount.service is solely responsible for mounting filesystems eliminating the race between "zfs mount -a" and "zfs share -a" commands. Reviewed-by: Sebastien Roy <email@example.com> Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Signed-off-by: George Wilson <email@example.com> Closes #9083cgit
|f9e3413a||hselasky||July 28, 2019, 9:47 p.m.||Add support for tethering with Nokia 7 plus and the alike.|
|b5965b56||rmacklem||July 28, 2019, 9:44 p.m.||Fix printing of Server Re-Failed and Server Faults.
nfsstat -s prints bogus large numbers for the Server Re-Failed and Server Faults fields. This was introduced by r328588. Although I know nothing about libxo, these lines aren't titles and this patch seems to fix the problem, so I am committing it for rea@ who emailed it to me. It also deleted the trailing ':' from the title lines, since those were not in the pre-r328588 output. If there is a more correct fix, someone conversant with libxo will need to do so. Submitted by: rea MFC after: 2 weekscgit ViewVC
|d7c1da61||mav||July 28, 2019, 8:17 p.m.||Decode some more IDENTIFY DEVICE bits.|
|23612f0d||dougm||July 28, 2019, 7:32 p.m.||In swap_pager_putpages, move the initialization of a free-blocks
counter, and the final freeing of freed swap blocks, outside the region where an object lock is held. Correct some style(9) and spelling errors. Change a panic() to a KASSERT(). Change a boolean_t to a bool. Suggested by: alc Reviewed by: alc Approved by: kib, markj (mentors) Differential Revision: https://reviews.freebsd.org/D21093cgit ViewVC
|05d49a82||asomers||July 28, 2019, 4:22 p.m.||MFHead @350390|
|e7d8ebc8||asomers||July 28, 2019, 4:07 p.m.||Better comments for vlrureclaim|
|06e1ffbc||asomers||July 28, 2019, 3:20 p.m.||[skip ci] Add me to MAINTAINERS for fusefs|
|669a092a||asomers||July 28, 2019, 3:17 p.m.||fusefs: fix panic when writing with O_DIRECT and using writeback cache
When a fusefs file system is mounted using the writeback cache, the cache may still be bypassed by opening a file with O_DIRECT. When writing with O_DIRECT, the cache must be invalidated for the affected portion of the file. Fix some panics caused by inadvertently invalidating too much. Sponsored by: The FreeBSD Foundationcgit ViewVC
|a63915c2||asomers||July 28, 2019, 4:02 a.m.||MFHead @r350386|
|2240d8c4||asomers||July 28, 2019, 12:48 a.m.||Add v_inval_buf_range, like vtruncbuf but for a range of a file
v_inval_buf_range invalidates all buffers within a certain LBA range of a file. It will be used by fusefs(5). This commit is a partial merge of r346162, r346606, and r346756 from projects/fuse2. Reviewed by: kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D21032cgit ViewVC
|1173e5a7||mav||July 27, 2019, 6:07 p.m.||Reenable UNMAP support on ramdisks by default.|