All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: RHEL 6.5 shared library upgrade safety
Date: Mon, 18 Aug 2014 13:57:16 +0200	[thread overview]
Message-ID: <53F1EA1C.1020108@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

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 ;-)

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

             reply	other threads:[~2014-08-18 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 11:57 Loic Dachary [this message]
2014-08-18 12:11 ` RHEL 6.5 shared library upgrade safety Wido den Hollander
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=53F1EA1C.1020108@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.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.