All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@icloud.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: osdmap consistency during incremental applying in kernel client
Date: Mon, 12 Feb 2018 12:05:51 +0800	[thread overview]
Message-ID: <302D379F-727B-489C-B257-633CF16577C8@icloud.com> (raw)

Hi All,

In ceph kernel client, osdmap_apply_incremental() can fail by failing of
allocation memory in many places, in this case, current osdmap can not
keep consistency after applying failure. 

I’m not sure how much impact will be caused by this kind of inconsistency
but for safety it’s better to keep osdmap consistency all the time even
failing from incremental applying. 

I’m trying to make some patches to fix this issue, but first of all please
let me know what do you think for this, I would be grateful if you could
share some ideas with me.



Thanks,
Chengguang.

             reply	other threads:[~2018-02-12  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  4:05 Chengguang Xu [this message]
2018-02-12  9:37 ` osdmap consistency during incremental applying in kernel client Ilya Dryomov
2018-02-12 10:44   ` Chengguang Xu
2018-02-12 10:52     ` Ilya Dryomov

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=302D379F-727B-489C-B257-633CF16577C8@icloud.com \
    --to=cgxu519@icloud.com \
    --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.