CEPH filesystem development
 help / color / mirror / Atom feed
From: xiubli@redhat.com
To: jlayton@kernel.org
Cc: idryomov@gmail.com, vshankar@redhat.com, lhenriques@suse.de,
	ceph-devel@vger.kernel.org, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v2 4/7] ceph: add ceph_get_snap_parent_inode() support
Date: Tue,  1 Mar 2022 19:30:12 +0800	[thread overview]
Message-ID: <20220301113015.498041-5-xiubli@redhat.com> (raw)
In-Reply-To: <20220301113015.498041-1-xiubli@redhat.com>

From: Xiubo Li <xiubli@redhat.com>

Get the parent inode for the snap directory ".snap", if the inode
is not a snap directory just return it with the reference increased.

Signed-off-by: Xiubo Li <xiubli@redhat.com>
---
 fs/ceph/snap.c  | 24 ++++++++++++++++++++++++
 fs/ceph/super.h |  1 +
 2 files changed, 25 insertions(+)

diff --git a/fs/ceph/snap.c b/fs/ceph/snap.c
index 66a1a92cf579..5e9656926dc7 100644
--- a/fs/ceph/snap.c
+++ b/fs/ceph/snap.c
@@ -1247,3 +1247,27 @@ void ceph_cleanup_snapid_map(struct ceph_mds_client *mdsc)
 		kfree(sm);
 	}
 }
+
+/*
+ * Get the parent inode for the snap directory ".snap",
+ * if the inode is not a snap directory just return it
+ * with the reference increased.
+ */
+struct inode *ceph_get_snap_parent_inode(struct inode *inode)
+{
+	struct inode *pinode;
+
+	if (ceph_snap(inode) == CEPH_SNAPDIR) {
+		struct ceph_vino vino = {
+			.ino = ceph_ino(inode),
+			.snap = CEPH_NOSNAP,
+		};
+		pinode = ceph_find_inode(inode->i_sb, vino);
+		BUG_ON(!pinode);
+	} else {
+		ihold(inode);
+		pinode = inode;
+	}
+
+	return pinode;
+}
diff --git a/fs/ceph/super.h b/fs/ceph/super.h
index d5a4d311f4c2..e7c69ca5e289 100644
--- a/fs/ceph/super.h
+++ b/fs/ceph/super.h
@@ -969,6 +969,7 @@ extern void ceph_put_snapid_map(struct ceph_mds_client* mdsc,
 				struct ceph_snapid_map *sm);
 extern void ceph_trim_snapid_map(struct ceph_mds_client *mdsc);
 extern void ceph_cleanup_snapid_map(struct ceph_mds_client *mdsc);
+extern struct inode *ceph_get_snap_parent_inode(struct inode *inode);
 void ceph_umount_begin(struct super_block *sb);
 
 
-- 
2.27.0


  parent reply	other threads:[~2022-03-01 11:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 11:30 [PATCH v2 0/7] ceph: encrypt the snapshot directories xiubli
2022-03-01 11:30 ` [PATCH v2 1/7] ceph: fail the request when failing to decode dentry names xiubli
2022-03-01 13:20   ` Jeff Layton
2022-03-01 13:57     ` Xiubo Li
2022-03-01 14:13       ` Jeff Layton
2022-03-01 11:30 ` [PATCH v2 2/7] ceph: skip the memories when received a higher version of message xiubli
2022-03-01 11:30 ` [PATCH v2 3/7] ceph: do not dencrypt the dentry name twice for readdir xiubli
2022-03-01 13:31   ` Jeff Layton
2022-03-01 14:05     ` Xiubo Li
2022-03-01 14:18       ` Jeff Layton
2022-03-01 14:33         ` Xiubo Li
2022-03-01 14:43           ` Jeff Layton
2022-03-01 14:45             ` Xiubo Li
2022-03-01 11:30 ` xiubli [this message]
2022-03-01 11:30 ` [PATCH v2 5/7] ceph: use the parent inode of '.snap' to dencrypt the names " xiubli
2022-03-01 11:30 ` [PATCH v2 6/7] ceph: use the parent inode of '.snap' to encrypt name to build path xiubli
2022-03-01 11:30 ` [PATCH v2 7/7] ceph: try to encrypt/decrypt long snap name xiubli

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=20220301113015.498041-5-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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox