Oops -- that was a mistake from George when he committed the fix, and I just propagated that mistake into the v1.8 pull request. I'll fix it there, at least. But the master commit message is unfortunately going to have to stay wrong. :-(
> On Apr 30, 2015, at 2:59 PM, Matthew Knepley <knep...@gmail.com> wrote: > > On Fri, May 1, 2015 at 4:55 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > Thank you! > > George reviewed your patch and adjusted it a bit. We applied it to master > and it's pending to the release series (v1.8.x). > > Was this identified by IBM? > > > https://github.com/open-mpi/ompi/commit/015d3f56cf749ee5ad9ea4428d2f5da72f9bbe08 > > Matt > > Would you mind testing a nightly master snapshot? It should be in tonight's > build: > > http://www.open-mpi.org/nightly/master/ > > > > > On Apr 30, 2015, at 12:50 AM, Satish Balay <ba...@mcs.anl.gov> wrote: > > > > OpenMPI developers, > > > > We've had issues (memory errors) with OpenMPI - and code in PETSc > > library that uses MPI_Win_fence(). > > > > Vagrind shows memory corruption deep inside OpenMPI function stack. > > > > I'm attaching a potential patch that appears to fix this issue for us. > > [the corresponding valgrind trace is listed in the patch header] > > > > Perhaps there is a more appropriate fix for this memory corruption. Could > > you check on this? > > > > [Sorry I don't have a pure MPI test code to demonstrate this error - > > but a PETSc test example code consistantly reproduces this issue] > > > > Thanks, > > Satish<openmpi-1.8.4.patch> > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
