mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for 4.11-rc2
Date: Fri, 10 Mar 2017 16:34:24 +0100	[thread overview]
Message-ID: <1489160064-26712-1-git-send-email-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:

  Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)

are available in the git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-4.11-rc2

for you to fetch changes up to 7cc5e38f2f0b0b58a22a4c18a56348dd99a71270:

  libceph: osd_request_timeout option (2017-03-07 14:30:38 +0100)

----------------------------------------------------------------
A fix for the recently discovered misdirected requests bug present in
jewel and later on the server side and all stable kernels, a fixup for
-rc1 CRUSH changes and two usability enhancements: osd_request_timeout
option and supported_features bus attribute.

----------------------------------------------------------------
Ilya Dryomov (4):
      libceph: fix crush_decode() for older maps
      libceph: don't set weight to IN when OSD is destroyed
      rbd: supported_features bus attribute
      libceph: osd_request_timeout option

 drivers/block/rbd.c             | 16 ++++++++++++----
 include/linux/ceph/libceph.h    |  2 ++
 include/linux/ceph/osd_client.h |  1 +
 net/ceph/ceph_common.c          | 15 +++++++++++++++
 net/ceph/osd_client.c           | 36 +++++++++++++++++++++++++++++++++++-
 net/ceph/osdmap.c               |  4 +---
 6 files changed, 66 insertions(+), 8 deletions(-)

                 reply	other threads:[~2017-03-10 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1489160064-26712-1-git-send-email-idryomov@gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®