All of lore.kernel.org
 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 updates for 5.5-rc1
Date: Wed,  4 Dec 2019 21:03:07 +0100	[thread overview]
Message-ID: <20191204200307.21047-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 219d54332a09e8d8741c1e1982f5eae56099de85:

  Linux 5.4 (2019-11-24 16:32:01 -0800)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-5.5-rc1

for you to fetch changes up to 82995cc6c5ae4bf4d72edef381a085e52d5b5905:

  libceph, rbd, ceph: convert to use the new mount API (2019-11-27 22:28:37 +0100)

----------------------------------------------------------------
The two highlights are a set of improvements to how rbd read-only
mappings are handled and a conversion to the new mount API (slightly
complicated by the fact that we had a common option parsing framework
that called out into rbd and the filesystem instead of them calling
into it).  Also included a few scattered fixes and a MAINTAINERS update
for rbd, adding Dongsheng as a reviewer.

----------------------------------------------------------------
Colin Ian King (1):
      rbd: fix spelling mistake "requeueing" -> "requeuing"

David Howells (1):
      libceph, rbd, ceph: convert to use the new mount API

Ilya Dryomov (11):
      libceph: drop unnecessary check from dispatch() in mon_client.c
      rbd: update MAINTAINERS info
      rbd: introduce rbd_is_snap()
      rbd: introduce RBD_DEV_FLAG_READONLY
      rbd: treat images mapped read-only seriously
      rbd: disallow read-write partitions on images mapped read-only
      rbd: don't acquire exclusive lock for read-only mappings
      rbd: don't establish watch for read-only mappings
      rbd: remove snapshot existence validation code
      rbd: don't query snapshot features
      rbd: ask for a weaker incompat mask for read-only mappings

Jeff Layton (3):
      ceph: make several helper accessors take const pointers
      ceph: tone down loglevel on ceph_mdsc_build_path warning
      ceph: don't leave ino field in ceph_mds_request_head uninitialized

Xiubo Li (1):
      ceph: fix geting random mds from mdsmap

 MAINTAINERS                  |   2 +-
 drivers/block/rbd.c          | 467 ++++++++++++++++---------------
 fs/ceph/cache.c              |   9 +-
 fs/ceph/cache.h              |   5 +-
 fs/ceph/mds_client.c         |  19 +-
 fs/ceph/mdsmap.c             |  11 +-
 fs/ceph/super.c              | 646 ++++++++++++++++++++++---------------------
 fs/ceph/super.h              |  13 +-
 include/linux/ceph/libceph.h |  10 +-
 net/ceph/ceph_common.c       | 419 +++++++++++++---------------
 net/ceph/messenger.c         |   2 -
 net/ceph/mon_client.c        |   3 -
 12 files changed, 803 insertions(+), 803 deletions(-)

             reply	other threads:[~2019-12-04 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 20:03 Ilya Dryomov [this message]
2019-12-05 21:19 ` [GIT PULL] Ceph updates for 5.5-rc1 Linus Torvalds
2019-12-06 11:05   ` Ilya Dryomov
2019-12-05 21:30 ` pr-tracker-bot

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=20191204200307.21047-1-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 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.