FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2 2015-06-15T18:16:23Z 2015-06-15T18:16:23Z Xin LI delphij@FreeBSD.org 2015-06-15T18:16:23Z urn:sha1:58ea82d0ddf4380040e521b063960f8cc8e12a93 Clear p_stops when doing PT_DETACH and PROCFS_CTL_DETACH. Without this, if a process was being traced by truss(1), which uses different p_stops bits than gdb(1), the latter would misbehave because of the unexpected bits. Reported by: jceel Submitted by: sef Sponsored by: iXsystems, Inc. 2015-06-13T16:15:43Z John Baldwin jhb@FreeBSD.org 2015-06-13T16:15:43Z urn:sha1:fbbf439256a5c9c48a32eb3063a476e570714060 Add KTR tracing for some MI ptrace events. 2015-01-05T03:27:09Z Konstantin Belousov kib@FreeBSD.org 2015-01-05T03:27:09Z urn:sha1:f11aebee48530f85c466b5d750d6dc4d84f5f705 MFC r270443 (by mjg): Properly reparent traced processes when the tracer dies. MFC r273452 (by mjg): Plug unnecessary PRS_NEW check in kern_procctl. MFC 275800: Add a facility for non-init process to declare itself the reaper of the orphaned descendants. MFC r275821: Add missed break. MFC r275846 (by mckusick): Add some additional clarification and fix a few gammer nits. MFC r275847 (by bdrewery): Bump Dd for r275846. 2014-10-17T19:28:21Z John Baldwin jhb@FreeBSD.org 2014-10-17T19:28:21Z urn:sha1:9adcf68cebcd3c87e93db22de281c5f66822a270 Require p_cansched() for changing a process' protection status via procctl() rather than p_cansee(). 2014-08-21T10:46:19Z Konstantin Belousov kib@FreeBSD.org 2014-08-21T10:46:19Z urn:sha1:04d46de6d9df43eaf529968493a9a8edb8c9e200 Implement and use proc_realparent(9). MFC r270024 (by markj): Correct the order of arguments passed to LIST_INSERT_AFTER(). For merge, the p_treeflag member of struct proc was moved to the end of the structure, to keep KBI intact. 2013-09-19T18:53:42Z John Baldwin jhb@FreeBSD.org 2013-09-19T18:53:42Z urn:sha1:55648840de371b7e4cb2704cb5d47d92dff11d45 exhausted. - Add a new protect(1) command that can be used to set or revoke protection from arbitrary processes. Similar to ktrace it can apply a change to all existing descendants of a process as well as future descendants. - Add a new procctl(2) system call that provides a generic interface for control operations on processes (as opposed to the debugger-specific operations provided by ptrace(2)). procctl(2) uses a combination of idtype_t and an id to identify the set of processes on which to operate similar to wait6(). - Add a PROC_SPROTECT control operation to manage the protection status of a set of processes. MADV_PROTECT still works for backwards compatability. - Add a p_flag2 to struct proc (and a corresponding ki_flag2 to kinfo_proc) the first bit of which is used to track if P_PROTECT should be inherited by new child processes. Reviewed by: kib, jilles (earlier version) Approved by: re (delphij) MFC after: 1 month 2013-08-05T08:55:35Z Attilio Rao attilio@FreeBSD.org 2013-08-05T08:55:35Z urn:sha1:be9968363742a7b369819f598be0d2f08f1c92ab We cannot busy a page before doing pagefaults. Infact, it can deadlock against vnode lock, as it tries to vget(). Other functions, right now, have an opposite lock ordering, like vm_object_sync(), which acquires the vnode lock first and then sleeps on the busy mechanism. Before this patch is reinserted we need to break this ordering. Sponsored by: EMC / Isilon storage division Reported by: kib 2013-08-04T21:07:24Z Attilio Rao attilio@FreeBSD.org 2013-08-04T21:07:24Z urn:sha1:3b6714cacb30c4ded64d5580426cf7acc9dfcd32 - It does not let pages respect the LRU policy - It bloats the active/inactive queues of few pages Try to avoid it as much as possible with the long-term target to completely remove it. Use the soft-busy mechanism to protect page content accesses during short-term operations (like uiomove_fromphys()). After this change only vm_fault_quick_hold_pages() is still using the hold mechanism for page content access. There is an additional complexity there as the quick path cannot immediately access the page object to busy the page and the slow path cannot however busy more than one page a time (to avoid deadlocks). Fixing such primitive can bring to complete removal of the page hold mechanism. Sponsored by: EMC / Isilon storage division Discussed with: alc Reviewed by: jeff Tested by: pho 2013-04-08T19:58:32Z Attilio Rao attilio@FreeBSD.org 2013-04-08T19:58:32Z urn:sha1:bc403f030d01afa9621b209d737d09d236037ba8 rather than write locks. Sponsored by: EMC / Isilon storage division Reviewed by: alc Tested by: pho 2013-03-09T02:32:23Z Attilio Rao attilio@FreeBSD.org 2013-03-09T02:32:23Z urn:sha1:89f6b8632cc94bca2738b4fcc26e1189ef4f5dde future further optimizations where the vm_object lock will be held in read mode most of the time the page cache resident pool of pages are accessed for reading purposes. The change is mostly mechanical but few notes are reported: * The KPI changes as follow: - VM_OBJECT_LOCK() -> VM_OBJECT_WLOCK() - VM_OBJECT_TRYLOCK() -> VM_OBJECT_TRYWLOCK() - VM_OBJECT_UNLOCK() -> VM_OBJECT_WUNLOCK() - VM_OBJECT_LOCK_ASSERT(MA_OWNED) -> VM_OBJECT_ASSERT_WLOCKED() (in order to avoid visibility of implementation details) - The read-mode operations are added: VM_OBJECT_RLOCK(), VM_OBJECT_TRYRLOCK(), VM_OBJECT_RUNLOCK(), VM_OBJECT_ASSERT_RLOCKED(), VM_OBJECT_ASSERT_LOCKED() * The vm/vm_pager.h namespace pollution avoidance (forcing requiring sys/mutex.h in consumers directly to cater its inlining functions using VM_OBJECT_LOCK()) imposes that all the vm/vm_pager.h consumers now must include also sys/rwlock.h. * zfs requires a quite convoluted fix to include FreeBSD rwlocks into the compat layer because the name clash between FreeBSD and solaris versions must be avoided. At this purpose zfs redefines the vm_object locking functions directly, isolating the FreeBSD components in specific compat stubs. The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). Sponsored by: EMC / Isilon storage division Reviewed by: jeff Reviewed by: pjd (ZFS specific review) Discussed with: alc Tested by: pho