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.
|38b06f8a||asomers||June 20, 2019, 11:07 p.m.||fcntl: fix overflow when setting F_READAHEAD
VOP_READ and VOP_WRITE take the seqcount in blocks in a 16-bit field. However, fcntl allows you to set the seqcount in bytes to any nonnegative 31-bit value. The result can be a 16-bit overflow, which will be sign-extended in functions like ffs_read. Fix this by sanitizing the argument in kern_fcntl. As a matter of policy, limit to IO_SEQMAX rather than INT16_MAX. Also, fifos have overloaded the f_seqcount field for a completely different purpose ever since r238936. Formalize that by using a union type. Reviewed by: cem MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D20710cgit ViewVC
|192a9181||asomers||June 20, 2019, 10:21 p.m.||fusefs: attempt to support servers as old as protocol 7.4
Previously we allowed servers as old as 7.1 to connect (there never was a 7.0). However, we wrongly assumed a few things about protocols older than 7.8. This commit attempts to support servers as old as 7.4 but no older. I added no new tests because I'm not sure there actually _are_ any servers this old in the wild. Sponsored by: The FreeBSD Foundationcgit ViewVC
|68035f63||mav||June 20, 2019, 10:20 p.m.||SPC-3 and up require some UAs to be returned as fixed.|
|ee37749a||brooks||June 20, 2019, 9:52 p.m.||Add PROT_MAX to the HISTORY section.
In the case of mmap(), add a HISTORY section. Mention that mmap() and mprotect()'s documentation predates an implementation. The implementation first saw wide use in 4.3-Reno, but there seems to be no easy way to express that in mdoc so stick with 4.4BSD. Reviewed by: emaste Requested by: cem Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D20713cgit ViewVC
|2ffddc5e||asomers||June 20, 2019, 9:29 p.m.||fusefs: raise protocol level to 7.13
This protocol version adds one new feature: the ability for the server to set the maximum number of background requests and a "congestion threshold" with ill-defined properties. I don't know of any fuse file systems in ports that use this feature, so I'm not implementing it. Sponsored by: The FreeBSD Foundationcgit ViewVC
|35a9ffc3||mav||June 20, 2019, 8:29 p.m.||Optimize xpt_getattr().
Do not allocate temporary buffer for attributes we are going to return as-is, just make sure to NUL-terminate them. Do not zero temporary 64KB buffer for CDAI_TYPE_SCSI_DEVID, XPT tells us how much data it filled and there are also length fields inside the returned data also. MFC after: 2 weeks Sponsored by: iXsystems, Inc.cgit ViewVC
|17795d82||np||June 20, 2019, 8:06 p.m.||cxgbe/t4_tom: DDP_DEAD is a ddp flag and not a toepcb flag.|
|da689887||behlendorf1||June 20, 2019, 7:29 p.m.||Allow unencrypted children of encrypted datasets
When encryption was first added to ZFS, we made a decision to prevent users from creating unencrypted children of encrypted datasets. The idea was to prevent users from inadvertently leaving some of their data unencrypted. However, since the release of 0.8.0, some legitimate reasons have been brought up for this behavior to be allowed. This patch simply removes this limitation from all code paths that had checks for it and updates the tests accordingly. Reviewed-by: Jason King <email@example.com> Reviewed-by: Sean Eric Fagan <firstname.lastname@example.org> Reviewed-by: Richard Laager <email@example.com> Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Signed-off-by: Tom Caputi <email@example.com> Closes #8737 Closes #8870cgit
|84b4201f||behlendorf1||June 20, 2019, 7:27 p.m.||Replace whereis with type in zfs-lib.sh
The whereis command should not be used since it may not exist in the initramfs. The dracut plymouth module also uses the type command instead of whereis. Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Reviewed-by: Garrett Fields <email@example.com> Signed-off-by: Dacian Reece-Stremtan <firstname.lastname@example.org> Closes #8920 Closes #8938cgit
|cb537974||emaste||June 20, 2019, 6:30 p.m.||Clarify vm_map_protect max_protection downgrade|
|74a1b66c||brooks||June 20, 2019, 6:24 p.m.||Extend mmap/mprotect API to specify the max page protections.
A new macro PROT_MAX() alters a protection value so it can be OR'd with a regular protection value to specify the maximum permissions. If present, these flags specify the maximum permissions. While these flags are non-portable, they can be used in portable code with simple ifdefs to expand PROT_MAX() to 0. This change allows (e.g.) a region that must be writable during run-time linking or JIT code generation to be made permanently read+execute after writes are complete. This complements W^X protections allowing more precise control by the programmer. This change alters mprotect argument checking and returns an error when unhandled protection flags are set. This differs from POSIX (in that POSIX only specifies an error), but is the documented behavior on Linux and more closely matches historical mmap behavior. In addition to explicit setting of the maximum permissions, an experimental sysctl vm.imply_prot_max causes mmap to assume that the initial permissions requested should be the maximum when the sysctl is set to 1. PROT_NONE mappings are excluded from this for compatibility with rtld and other consumers that use such mappings to reserve address space before mapping contents into part of the reservation. A final version this is expected to provide per-binary and per-process opt-in/out options and this sysctl will go away in its current form. As such it is undocumented. Reviewed by: emaste, kib (prior version), markj Additional suggestions from: alc Obtained from: CheriBSD Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D18880cgit ViewVC
|0cf19786||emaste||June 20, 2019, 6:19 p.m.||Clarify that vm_map_protect cannot upgrade max_protection
It's implied by the man page's RETURN VALUES section, but be explicit in the description that vm_map_protect can not set new protection bits that are already in each entry's max_protection. Reviewed by: brooks MFC After: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D20709cgit ViewVC
|a1c9f4ad||asomers||June 20, 2019, 5:08 p.m.||fusefs: implement VOP_BMAP
If the fuse daemon supports FUSE_BMAP, then use that for the block mapping. Otherwise, use the same technique used by vop_stdbmap. Report large values for runp and runb in order to maximize read clustering and minimize upcalls, even if we don't know the true layout. The major result of this change is that sequential reads to FUSE files will now usually happen 128KB at a time instead of 64KB. Sponsored by: The FreeBSD Foundationcgit ViewVC
|67056e3d||asomers||June 20, 2019, 4:36 p.m.||VOP_REVOKE(9): update locking requirements per r143495|
|e532a999||asomers||June 20, 2019, 3:56 p.m.||MFHead @349234|