On Tue, 2016-08-02 at 22:25 +0300, Konstantin Belousov wrote: > Below is the merge of some high-profile virtual memory subsystem bug > fixes from stable/10 to 10.3. I merged fixes for bugs reported by > users, issues which are even theoretically unlikely to occur in real > world loads, are not included into the patch set. The later is mostly > corrections for the handling of radix insertion failures. Included > fixes > are for random SIGSEGV delivered to processes, hangs on "vodead" > state > on filesystem operations, and several others. > > List of the merged revisions: > r301184 prevent parallel object collapses, fixes object lifecycle > r301436 do not leak the vm object lock, fixes overcommit disable > r302243 avoid the active object marking for vm.vmtotal sysctl, fixes > "vodead" hangs > r302513 vm_fault() race with the vm_object_collapse(), fixes spurious > SIGSEGV > r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim > > I am asking for some testing, it is not necessary for your system to > exhibit the problematic behaviour for your testing to be useful. I am > more looking for smoke-testing kind of confirmation that patch is > fine. > Neither I nor people who usually help me with testing, run 10.3 > systems. > > If everything appear to be fine, my intent is to ask re/so to issue > Errata Notice with these changes in about a week from now. > > Index: sys/kern/vfs_subr.c > [...]
I run 10-stable on my everyday desktop/build machine, but my mail client ruined the format of the patches. Can I just 'svn up' on the 10 -stable branch and then MFC the revs you list above, or are there hand -tweaks to the patches you attached? -- Ian _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
