LKML 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 fixes for 6.4-rc6
Date: Fri,  9 Jun 2023 18:31:42 +0200	[thread overview]
Message-ID: <20230609163142.16428-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 9561de3a55bed6bdd44a12820ba81ec416e705a7:

  Linux 6.4-rc5 (2023-06-04 14:04:27 -0400)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-6.4-rc6

for you to fetch changes up to 409e873ea3c1fd3079909718bbeb06ac1ec7f38b:

  ceph: fix use-after-free bug for inodes when flushing capsnaps (2023-06-08 08:56:25 +0200)

----------------------------------------------------------------
A fix for a potential data corruption in differential backup and
snapshot-based mirroring scenarios in RBD and a reference counting
fixup to avoid use-after-free in CephFS, all marked for stable.

----------------------------------------------------------------
Ilya Dryomov (2):
      rbd: move RBD_OBJ_FLAG_COPYUP_ENABLED flag setting
      rbd: get snapshot context after exclusive lock is ensured to be held

Xiubo Li (1):
      ceph: fix use-after-free bug for inodes when flushing capsnaps

 drivers/block/rbd.c | 62 +++++++++++++++++++++++++++++++++++++----------------
 fs/ceph/caps.c      |  6 ++++++
 fs/ceph/snap.c      |  4 +++-
 3 files changed, 53 insertions(+), 19 deletions(-)

             reply	other threads:[~2023-06-09 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 16:31 Ilya Dryomov [this message]
2023-06-09 18:19 ` [GIT PULL] Ceph fixes for 6.4-rc6 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=20230609163142.16428-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 read-only IMAP folder(s) and NNTP newsgroup(s).