Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI devel] (no subject)
From: ananda.mudar_at_[hidden]
Date: 2010-11-30 00:07:12

Jeff, George, Ralph

Thanks a lot for your clarifications!!

- Ananda

----------- PREVIOUS MESSAGE -----------------------

Subject: Re: [OMPI devel] Warning on fork() disappears if I use MPI
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2010-11-29 19:50:33

* Previous message: Ralph Castain: "Re: [OMPI devel] Warning on
fork() disappears if I use MPI threads!!"
* In reply to: George Bosilca: "Re: [OMPI devel] Warning on fork()
disappears if I use MPI threads!!"
* Next in thread: Ralph Castain: "Re: [OMPI devel] Warning on
fork() disappears if I use MPI threads!!"


On Nov 29, 2010, at 6:25 PM, George Bosilca wrote:

> The main problem is that openib require to pin memory pages in order
to take advantage of RMA features. There is a major issues with these
pinned pages and fork, leading to segmentation fault in some specific
cases. However, we only pin the pages on the MPI calls related to data
transfers. Therefore, if you call fork __before__ any other MPI data
transfer function (but after MPI_Init as you use the process rank), your
application should be safe.

Note that Open MPI also pins some internal memory during MPI_INIT, but
that memory is totally internal to libmpi, so you should be safe (i.e.,
you should never be able to find it and therefore never be able to try
to touch it).

>> How can one be sure that the disabling the warning is ok? Could you
please elaborate on what makes forks vulnerable? May be that will guide
the developers to make an informed decision on whether to disable them
or find another alternative.
> No way to know at 100%. Now for an elaborate answer: Once upon a time
... The fork story is a long and boring one, we would all have preferred
to never heard about it (believe me). A quick and compressed version can
be found on the QLogic download page

That's a good summary. The issue is with OFED itself, not with Open MPI.

Note, too, that calling popen() should also be safe (even though we'll
warn about it -- our atfork hook has no way of knowing whether you're
calling system, popen, or something else).

Jeff Squyres
For corporate legal information go to:
Ananda B Mudar, PMP
Senior Technical Architect
Wipro Technologies
Ph: 972 765 8093
Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.