linux-kernel.vger.kernel.org archive mirror
 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 4.19-rc3
Date: Fri,  7 Sep 2018 19:06:43 +0200	[thread overview]
Message-ID: <20180907170643.18214-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 57361846b52bc686112da6ca5368d11210796804:

  Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-4.19-rc3

for you to fetch changes up to e92c0eaf754310f9f31e9229a3f7274a67478f82:

  rbd: support cloning across namespaces (2018-09-06 16:18:04 +0200)

----------------------------------------------------------------
Two rbd patches to complete support for images within namespaces that
went into -rc1 and a use-after-free fix.

The rbd changes have been sitting in a branch for quite a while but
couldn't be included into the -rc1 pull request because of a pending
wire protocol backwards compatibility fixup that only got committed
early this week.

Said fixup ended up being really trivial -- just an extra byte added,
so I decided to send these changes for -rc3.  If it's too late in the
cycle for this follow-up to be pulled, let me know and I'll send the
use-after-free fix separately; we will have the necessary stop gaps on
the server side to prevent the current 4.19 code from doing anything
unexpected.

----------------------------------------------------------------
Ilya Dryomov (3):
      ceph: avoid a use-after-free in ceph_destroy_options()
      rbd: factor out get_parent_info()
      rbd: support cloning across namespaces

 drivers/block/rbd.c | 235 +++++++++++++++++++++++++++++++++++++++-------------
 fs/ceph/super.c     |  16 ++--
 2 files changed, 189 insertions(+), 62 deletions(-)

                 reply	other threads:[~2018-09-07 17:07 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=20180907170643.18214-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).