mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sage Weil <sweil@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for -rc6
Date: Thu, 28 Apr 2016 10:08:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.1604281006521.25990@cpach.fuggernut.com> (raw)

Hi Linus,

  git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus

There is a lifecycle fix in the auth code, a fix for a narrow race 
condition on map, and a helpful message in the log when there is a feature 
mismatch (which happens frequently now that the default server-side 
options have changed).

Thanks!
sage



----------------------------------------------------------------
Ilya Dryomov (3):
      libceph: make authorizer destruction independent of ceph_auth_client
      rbd: fix rbd map vs notify races
      rbd: report unsupported features to syslog

 drivers/block/rbd.c             | 52 +++++++++++++++---------------
 fs/ceph/mds_client.c            |  6 ++--
 include/linux/ceph/auth.h       | 10 +++---
 include/linux/ceph/osd_client.h |  1 -
 net/ceph/auth.c                 |  8 ++---
 net/ceph/auth_none.c            | 71 ++++++++++++++++++++++-------------------
 net/ceph/auth_none.h            |  3 +-
 net/ceph/auth_x.c               | 21 ++++++------
 net/ceph/auth_x.h               |  1 +
 net/ceph/osd_client.c           |  6 ++--
 10 files changed, 87 insertions(+), 92 deletions(-)

             reply	other threads:[~2016-04-28 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 14:08 Sage Weil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-26 16:05 Sage Weil
2015-10-16 15:20 Sage Weil
2015-08-03 14:39 Sage Weil
2014-05-16 19:59 Sage Weil
2013-06-11 20:24 Sage Weil
2011-12-13 20:36 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=alpine.DEB.2.11.1604281006521.25990@cpach.fuggernut.com \
    --to=sweil@redhat.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®