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.
|ec5753e0||pfg||Jan. 20, 2017, 12:02 a.m.||mppc - Finish pluging NETGRAPH_MPPC_COMPRESSION.
There were several places where reference to compression were left unfinished. Furthermore, KASSERTs contained references to MPPC_INVALID which is not defined in the tree and therefore were sure to break with INVARIANTS: comment them out. Reported by: Eugene Grosbein PR: 216265 MFC after: 3 dayscgit ViewVC
|2d4d81c4||behlendorf1||Jan. 19, 2017, 10:41 p.m.||Reimplement rt_mutex_owner to fix build with DEBUG & PREEMPT_RT_FULL
rt_mutex_owner is internal to kernel/locking/rtmutex_common.h and inaccessible for SPL via the public kernel headers. The way of accessing the owner has been stable since at least 3.13 (, ), which is masking the lowest bit in the owner pointer in rt_mutex. We do the same.  http://lxr.free-electrons.com/source/kernel/locking/rtmutex_common.h?v=3.13#L99  http://lxr.free-electrons.com/source/kernel/locking/rtmutex_common.h?v=4.9#L78 Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Signed-off-by: Clemens Fruhwirth <email@example.com> Closes #593cgit
|5cb44271||behlendorf1||Jan. 19, 2017, 10:32 p.m.||Remove identical if statements in module/spl/spl-vnode.c|
|61673a1f||jkim||Jan. 19, 2017, 10:07 p.m.||Merge ACPICA 20170119.|
|040dab99||behlendorf1||Jan. 19, 2017, 9:56 p.m.||Suspend/resume zvol for recv and rollback
When doing recv and rollback, dsl_dataset_clone_swap_sync_impl will be called to swap out the ds_objset and do dmu_objset_evict on the old one. However, currently zv->zv_objset will not be swapped out accordingly, so if anyone currently holds a fd on the zvol, we risk hitting a use-after-free. We fix this by introducing the suspend and resume mechanism of zsb to zv. Before recv or rollback, we use zvol_suspend to block all access to zv_objset and shut it down. After the recv or rollback, we use zvol_resume to swap in zv_objset with the new ds_objset and unblock the access. Reviewed-by: Brian Behlendorf <firstname.lastname@example.org> Signed-off-by: Chunwei Chen <email@example.com> Closes #4866 Closes #5609cgit
|76fe529b||behlendorf1||Jan. 19, 2017, 9:50 p.m.||OpenZFS 6529 - Properly handle updates of variably-sized SA entries
Porting notes: - This issue was first fixed in ZoL by commit d862cb0d. That fix was then modified and an equivalent version of the patch landed in the upstream code base. For additional details see the discussion in https://github.com/openzfs/openzfs/pull/24 . This commit aligns ZoL with OpenZFS codebase. Authored by: Andriy Gapon <firstname.lastname@example.org> Reviewed by: Brian Behlendorf <email@example.com> Reviewed by: Matthew Ahrens <firstname.lastname@example.org> Reviewed by: Ned Bass <email@example.com> Reviewed by: Tim Chase <firstname.lastname@example.org> Approved by: Gordon Ross <email@example.com> Ported-by: George Melikov firstname.lastname@example.org OpenZFS-issue: https://www.illumos.org/issues/6529 OpenZFS-commit: https://github.com/openzfs/openzfs/commit/e7e978b Closes #5606cgit
|c11c484f||scottl||Jan. 19, 2017, 9:47 p.m.||Rework the debug print API. Event printing no longer gets special handling.
All of the printing from the tables file now has wrappers so that the handling is cleaner and it's possible to print something out (say, during development) without having to fight the global debug flags. This re-org will also make it easier to have the tables be compiled out at build time if desired. Other than fixing some minor bugs, there are no user-visible changes from this change Sponsored by: Netflix, Inc. Differential Revision: D9238cgit ViewVC
|1e37d7e5||jpaetzel||Jan. 19, 2017, 8:44 p.m.||6569 large file delete can starve out write ops
illumos/illumos-gate@ff5177ee8bf9a355131ce2cc61ae2da6a5a6fdd6 https://github.com/illumos/illumos-gate/commit/ff5177ee8bf9a355131ce2cc61ae2da6a5a6fdd6 https://www.illumos.org/issues/6569 The core issue I've found is that there is no throttle for how many deletes get assigned to one TXG. As a results when deleting large files we end up filling consecutive TXGs with deletes/frees, then write throttling other (more important) ops. There is an easy test case for this problem. Try deleting several large files (at least 1/2 TB) while you do write ops on the same pool. What we've seen is performance of these write ops (let's call it sideload I/O) would drop to zero. More specifically the problem is that dmu_free_long_range_impl() can/will fill up all of the dirty data in the pool "instantly", before many of the sideload ops can get in. So sideload performance will be impacted until all the files are freed. The solution we have tested at Nexenta (with positive results) creates a relatively simple throttle for how many "free" ops we let into one TXG. However this solution exposes other problems that should also be addressed. If we are to slow down freeing of data that means one has to wait even longer (assuming vnode ref count of 1) to get shell back after an rm or for NFS thread to finish the free-ing op. To avoid this the proposed solution is to call zfs_inactive() async for "large" files. Async freeing then begs for the reclaimed space to be accounted for in the zpool's "freeing" prop. The other issue with having a longer delete is the inability to export/unmount for a longer period of time. The proposed solution is to interrupt freeing of blocks when a fs is unmounted. Author: Alek Pinchuk <email@example.com> Reviewed by: Matt Ahrens <firstname.lastname@example.org> Reviewed by: Sanjay Nadkarni <email@example.com> Reviewed by: Pavel Zakharov <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>cgit ViewVC
|538ee0d7||kib||Jan. 19, 2017, 8:03 p.m.||Remove mistakenly merged field.|
|d23d2945||sbruno||Jan. 19, 2017, 7:58 p.m.||Adjust gtaskqueue startup again so that we catch the !SMP case and|
|00ac6a98||kib||Jan. 19, 2017, 7:46 p.m.||Add mount option for tmpfs(5) to not use namecache.
The option "nonc" disables using of namecache for the created mount, by default namecache is used. The rationale for the option is that namecache duplicates the information which is already kept in memory by tmpfs. Since it believed that namecache scales better than tmpfs, or will scale better, do not enable the option by default. On the other hand, smaller machines may benefit from lesser namecache pressure. Discussed with: mjg Tested by: pho (as part of larger patch) Sponsored by: The FreeBSD Foundation MFC after: 2 weekscgit ViewVC
|a0b3a9cf||jkim||Jan. 19, 2017, 7:46 p.m.||Import ACPICA 20170119.|
|08c053e7||kib||Jan. 19, 2017, 7:29 p.m.||Implement VOP_VPTOCNP() for tmpfs.
For directories, node->tn_spec.tn_dir.tn_parent pointer to the parent is used. For non-directories, the implementation is naive, all directory nodes are scanned to find a dirent linking the specified node. This can be significantly improved by maintaining tn_parent for all nodes, later. Tested by: pho (as part of larger patch) Sponsored by: The FreeBSD Foundation MFC after: 2 weekscgit ViewVC
|b4ba3b64||kib||Jan. 19, 2017, 7:25 p.m.||VNON nodes cannot exist.|
|64c25043||kib||Jan. 19, 2017, 7:15 p.m.||Refcount tmpfs nodes and mount structures.
On dotdot lookup and fhtovp operations, it is possible for the file represented by tmpfs node to be removed after the thread calculated the pointer. In this case, tmpfs_alloc_vp() accesses freed memory. Introduce the reference count on the nodes. The allnodes list from tmpfs mount owns 1 reference, and threads performing unlocked operations on the node, add one transient reference. Similarly, since struct tmpfs_mount maintains the list where nodes are enlisted, refcount it by one reference from struct mount and one reference from each node on the list. Both nodes and tmpfs_mounts are removed when refcount goes to zero. Note that this means that nodes and tmpfs_mounts might survive some time after the node is deleted or tmpfs_unmount() finished. The tmpfs_alloc_vp() in these cases returns error either due to node removal (tn_nlinks == 0) or because of insmntque1(9) error. Tested by: pho (as part of larger patch) Sponsored by: The FreeBSD Foundation MFC after: 2 weekscgit ViewVC