From: Wido den Hollander <wido@42on.com>
To: Loic Dachary <loic@dachary.org>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RHEL 6.5 shared library upgrade safety
Date: Mon, 18 Aug 2014 14:11:00 +0200 [thread overview]
Message-ID: <53F1ED54.2020109@42on.com> (raw)
In-Reply-To: <53F1EA1C.1020108@dachary.org>
On 08/18/2014 01:57 PM, Loic Dachary wrote:
> Hi Ceph,
>
> In RHEL 6.5, is the following scenario possible :
>
> a) an OSD dlopen a shared library for erasure-code,
> b) the shared library file is replaced while the OSD is running,
> c) the OSD starts using the new file instead of the old one.
>
> It seems unlikely but it would explain a weird stack trace at http://tracker.ceph.com/issues/9153#note-5 so I'm double checking ;-)
>
Well, it could be that it does so. I'm not 100% sure, but afaik it could
happen that when you replace a library certain parts might not be in memory.
See:
http://stackoverflow.com/questions/7767325/replacing-shared-object-so-file-while-main-program-is-running
> Cheers
>
--
Wido den Hollander
Ceph consultant and trainer
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2014-08-18 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 11:57 RHEL 6.5 shared library upgrade safety Loic Dachary
2014-08-18 12:11 ` Wido den Hollander [this message]
2014-08-18 14:06 ` Loic Dachary
2014-08-18 15:17 ` Sage Weil
2014-08-18 15:25 ` Loic Dachary
2014-08-18 15:32 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F1ED54.2020109@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.