On Tue, Aug 02, 2016 at 12:47:23PM -0700, pete wright wrote:
> On Aug 2, 2016 12:26 PM, "Konstantin Belousov" <kostik...@gmail.com> 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.
> >
> 
> Is testing on 10.3-RELEASE useful, or is this only for people tracking
> STABLE?
This is only for people running 10.3.  The list of merged revisions is from
stable/10, where the fixes were already merged for month or more.
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to