From: xiubli@redhat.com
To: idryomov@gmail.com, ceph-devel@vger.kernel.org
Cc: jlayton@kernel.org, mchangir@redhat.com, vshankar@redhat.com,
lhenriques@suse.de, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v7 0/2] ceph: blocklist the kclient when receiving corrupted snap trace
Date: Wed, 1 Feb 2023 09:36:43 +0800 [thread overview]
Message-ID: <20230201013645.404251-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
V7:
- fix the debug log
- reorder the fence io and request's err checking
- remove stray whitespace
V6:
- switch to ceph_inode_is_shutdown() to check the mount state
- fix two debug logs
- use the WRITE_ONCE to set the FENCE_IO state
V5:
- s/CEPH_MOUNT_CORRUPTED/CEPH_MOUNT_FENCE_IO/g
V4:
- block all the IO/metadata requests before evicting the client.
V3:
- Fixed ERROR: spaces required around that ':' (ctx:VxW)
V2:
- Switched to WARN() to taint the Linux kernel.
Xiubo Li (2):
ceph: move mount state enum to fs/ceph/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 | 9 +++++++++
fs/ceph/mds_client.c | 28 +++++++++++++++++++++++---
fs/ceph/snap.c | 38 ++++++++++++++++++++++++++++++++++--
fs/ceph/super.h | 11 +++++++++++
include/linux/ceph/libceph.h | 10 ----------
7 files changed, 109 insertions(+), 20 deletions(-)
--
2.31.1
next reply other threads:[~2023-02-01 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 1:36 xiubli [this message]
2023-02-01 1:36 ` [PATCH v7 1/2] ceph: move mount state enum to fs/ceph/super.h xiubli
2023-02-01 1:36 ` [PATCH v7 2/2] ceph: blocklist the kclient when receiving corrupted snap trace xiubli
2023-02-01 13:12 ` Ilya Dryomov
2023-02-02 2:30 ` Xiubo Li
2023-02-02 13:11 ` Ilya Dryomov
2023-02-02 13:47 ` Xiubo Li
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=20230201013645.404251-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=mchangir@redhat.com \
--cc=vshankar@redhat.com \
/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.