From: Peng Tao <bergwolf@gmail.com>
To: Fengnan Chang <changfengnan@vivo.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2] fuse: use newer inode info when writeback cache is enabled
Date: Mon, 16 Aug 2021 10:48:06 +0800 [thread overview]
Message-ID: <CA+a=Yy5UzTUvS+JvtRtD=tUw0-UG4k=THdHMaXYEqOymo8g6UQ@mail.gmail.com> (raw)
In-Reply-To: <c5982115-e62c-908c-8aac-011ca682f193@vivo.com>
On Tue, Aug 10, 2021 at 3:12 PM Fengnan Chang <changfengnan@vivo.com> wrote:
>
> Remove cache=always still have this problem, this problem is related
> about FUSE_CAP_WRITEBACK_CACHE.
FUSE_CAP_WRITEBACK_CACHE by definition asks the kernel to trust its
own inode attributes. So I don't think we should fix its semantics.
Instead, in your case, it seems that the two mnts (PATHA and PATHB)
are not sharing the same superblock. I would suggest fixing it at a
higher level:
1. use bind-mount to mount PATHA and PATHB,
2. or add a `tag=xxx` argument to fuse mount option to uniquely
identify a fuse file system (just like we do in the virtiofs case)
Cheers,
Tao
--
Into Sth. Rich & Strange
next prev parent reply other threads:[~2021-08-16 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 8:50 [PATCH v2] fuse: use newer inode info when writeback cache is enabled Fengnan Chang
2021-05-07 10:04 ` Fengnan Chang
2021-06-22 7:59 ` Miklos Szeredi
2021-06-22 12:25 ` Fengnan Chang
2021-06-22 15:19 ` Miklos Szeredi
2021-06-24 7:42 ` Fengnan Chang
2021-06-25 3:42 ` Fengnan Chang
2021-08-06 12:20 ` Miklos Szeredi
2021-08-10 1:41 ` Fengnan Chang
2021-08-16 2:48 ` Peng Tao [this message]
2021-05-07 10:09 changfengnan
2021-05-11 11:21 ` 答复: " changfengnan
2021-05-12 12:33 ` Miklos Szeredi
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='CA+a=Yy5UzTUvS+JvtRtD=tUw0-UG4k=THdHMaXYEqOymo8g6UQ@mail.gmail.com' \
--to=bergwolf@gmail.com \
--cc=changfengnan@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.