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 fix for 6.2-rc7
Date: Fri,  3 Feb 2023 19:13:13 +0100	[thread overview]
Message-ID: <20230203181313.452449-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 6d796c50f84ca79f1722bb131799e5a5710c4700:

  Linux 6.2-rc6 (2023-01-29 13:59:43 -0800)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-6.2-rc7

for you to fetch changes up to a68e564adcaa69b0930809fb64d9d5f7d9c32ba9:

  ceph: blocklist the kclient when receiving corrupted snap trace (2023-02-02 13:58:15 +0100)

----------------------------------------------------------------
A safeguard to prevent the kernel client from further damaging the
filesystem after running into a case of an invalid snap trace.  The
root cause of this metadata corruption is still being investigated but
it appears to be stemming from the MDS.  As such, this is the best we
can do for now.

----------------------------------------------------------------
Xiubo Li (2):
      ceph: move mount state enum to super.h
      ceph: blocklist the kclient when receiving corrupted snap trace

 fs/ceph/addr.c               | 17 +++++++++++++++--
 fs/ceph/caps.c               | 16 +++++++++++++---
 fs/ceph/file.c               |  3 +++
 fs/ceph/mds_client.c         | 30 +++++++++++++++++++++++++++---
 fs/ceph/snap.c               | 36 ++++++++++++++++++++++++++++++++++--
 fs/ceph/super.h              | 11 +++++++++++
 include/linux/ceph/libceph.h | 10 ----------
 7 files changed, 103 insertions(+), 20 deletions(-)

             reply	other threads:[~2023-02-03 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 18:13 Ilya Dryomov [this message]
2023-02-03 18:45 ` 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=20230203181313.452449-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

all inboxes | Powered by JetHome®