mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: dhowells@redhat.com, linux-cachefs@redhat.com, xiang@kernel.org,
	chao@kernel.org, linux-erofs@lists.ozlabs.org
Cc: torvalds@linux-foundation.org, gregkh@linuxfoundation.org,
	willy@infradead.org, linux-fsdevel@vger.kernel.org,
	joseph.qi@linux.alibaba.com, bo.liu@linux.alibaba.com,
	tao.peng@linux.alibaba.com, gerry@linux.alibaba.com,
	eguan@linux.alibaba.com, linux-kernel@vger.kernel.org,
	luodaowen.backend@bytedance.com, tianzichen@kuaishou.com,
	fannaihao@baidu.com
Subject: [PATCH v7 13/19] erofs: register fscache context for primary data blob
Date: Thu, 31 Mar 2022 19:57:47 +0800	[thread overview]
Message-ID: <20220331115753.89431-14-jefflexu@linux.alibaba.com> (raw)
In-Reply-To: <20220331115753.89431-1-jefflexu@linux.alibaba.com>

Registers fscache context for primary data blob. Also move the
initialization of s_op and related fields forward, since anonymous
inode will be allocated under the super block when registering the
fscache context.

Something worth mentioning about the cleanup routine.

1. The fscache context will instantiate anonymous inodes under the super
block. Release these anonymous inodes when .put_super() is called, or
we'll get "VFS: Busy inodes after unmount." warning.

2. The fscache context is initialized prior to the root inode. If
.kill_sb() is called when mount failed, .put_super() won't be called
when root inode has not been initialized yet. Thus .kill_sb() shall
also contain the cleanup routine.

Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
---
 fs/erofs/internal.h |  1 +
 fs/erofs/super.c    | 15 +++++++++++----
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/fs/erofs/internal.h b/fs/erofs/internal.h
index 3a4a344cfed3..eb37b33bce37 100644
--- a/fs/erofs/internal.h
+++ b/fs/erofs/internal.h
@@ -155,6 +155,7 @@ struct erofs_sb_info {
 
 	/* fscache support */
 	struct fscache_volume *volume;
+	struct erofs_fscache *s_fscache;
 };
 
 #define EROFS_SB(sb) ((struct erofs_sb_info *)(sb)->s_fs_info)
diff --git a/fs/erofs/super.c b/fs/erofs/super.c
index 6590ed1b7d3b..9498b899b73b 100644
--- a/fs/erofs/super.c
+++ b/fs/erofs/super.c
@@ -585,6 +585,9 @@ static int erofs_fc_fill_super(struct super_block *sb, struct fs_context *fc)
 	int err;
 
 	sb->s_magic = EROFS_SUPER_MAGIC;
+	sb->s_flags |= SB_RDONLY | SB_NOATIME;
+	sb->s_maxbytes = MAX_LFS_FILESIZE;
+	sb->s_op = &erofs_sops;
 
 	if (!sb_set_blocksize(sb, EROFS_BLKSIZ)) {
 		erofs_err(sb, "failed to set erofs blksize");
@@ -605,6 +608,11 @@ static int erofs_fc_fill_super(struct super_block *sb, struct fs_context *fc)
 		err = erofs_fscache_register_fs(sb);
 		if (err)
 			return err;
+
+		err = erofs_fscache_register_cookie(sb, &sbi->s_fscache,
+						    sbi->opt.fsid, true);
+		if (err)
+			return err;
 	}
 
 	err = erofs_read_superblock(sb);
@@ -619,11 +627,8 @@ static int erofs_fc_fill_super(struct super_block *sb, struct fs_context *fc)
 			clear_opt(&sbi->opt, DAX_ALWAYS);
 		}
 	}
-	sb->s_flags |= SB_RDONLY | SB_NOATIME;
-	sb->s_maxbytes = MAX_LFS_FILESIZE;
-	sb->s_time_gran = 1;
 
-	sb->s_op = &erofs_sops;
+	sb->s_time_gran = 1;
 	sb->s_xattr = erofs_xattr_handlers;
 
 	if (test_opt(&sbi->opt, POSIX_ACL))
@@ -763,6 +768,7 @@ static void erofs_kill_sb(struct super_block *sb)
 
 	erofs_free_dev_context(sbi->devs);
 	fs_put_dax(sbi->dax_dev);
+	erofs_fscache_unregister_cookie(&sbi->s_fscache);
 	erofs_fscache_unregister_fs(sb);
 	kfree(sbi);
 	sb->s_fs_info = NULL;
@@ -781,6 +787,7 @@ static void erofs_put_super(struct super_block *sb)
 	iput(sbi->managed_cache);
 	sbi->managed_cache = NULL;
 #endif
+	erofs_fscache_unregister_cookie(&sbi->s_fscache);
 }
 
 static struct file_system_type erofs_fs_type = {
-- 
2.27.0


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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 11:57 [PATCH v7 00/19] fscache,erofs: fscache-based on-demand read semantics Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 01/19] cachefiles: extract write routine Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 02/19] cachefiles: notify user daemon with anon_fd when looking up cookie Jeffle Xu
2022-04-02  5:32   ` JeffleXu
2022-03-31 11:57 ` [PATCH v7 03/19] cachefiles: notify user daemon when withdrawing cookie Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 04/19] cachefiles: implement on-demand read Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 05/19] cachefiles: enable on-demand read mode Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 06/19] cachefiles: document " Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 07/19] erofs: make erofs_map_blocks() generally available Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 08/19] erofs: add mode checking helper Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 09/19] erofs: register fscache volume Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 10/19] erofs: add fscache context helper functions Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 11/19] erofs: add anonymous inode managing page cache for data blob Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 12/19] erofs: add erofs_fscache_read_folios() helper Jeffle Xu
2022-03-31 11:57 ` Jeffle Xu [this message]
2022-03-31 11:57 ` [PATCH v7 14/19] erofs: register fscache context for extra data blobs Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 15/19] erofs: implement fscache-based metadata read Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 16/19] erofs: implement fscache-based data read for non-inline layout Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 17/19] erofs: implement fscache-based data read for inline layout Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 18/19] erofs: implement fscache-based data readahead Jeffle Xu
2022-03-31 11:57 ` [PATCH v7 19/19] erofs: add 'fsid' mount option Jeffle Xu
2022-03-31 23:56 ` [PATCH v7 00/19] fscache,erofs: fscache-based on-demand read semantics JeffleXu

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=20220331115753.89431-14-jefflexu@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=bo.liu@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=eguan@linux.alibaba.com \
    --cc=fannaihao@baidu.com \
    --cc=gerry@linux.alibaba.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luodaowen.backend@bytedance.com \
    --cc=tao.peng@linux.alibaba.com \
    --cc=tianzichen@kuaishou.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.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®