From: Christian Brauner <brauner@kernel.org>
To: Baokun Li <libaokun@huaweicloud.com>
Cc: Jeff Layton <jlayton@kernel.org>,
netfs@lists.linux.dev, dhowells@redhat.com,
hsiangkao@linux.alibaba.com, jefflexu@linux.alibaba.com,
zhujia.zj@bytedance.com, linux-erofs@lists.ozlabs.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
yangerkun@huawei.com, houtao1@huawei.com, yukuai3@huawei.com,
wozizhi@huawei.com, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH v2 2/5] cachefiles: flush all requests for the object that is being dropped
Date: Thu, 27 Jun 2024 17:18:40 +0200 [thread overview]
Message-ID: <20240627-beizeiten-hecht-0efad69e0e38@brauner> (raw)
In-Reply-To: <e40b80fc-52b8-4f89-800a-3ffa0034a072@huaweicloud.com>
On Thu, Jun 27, 2024 at 07:20:16PM GMT, Baokun Li wrote:
> On 2024/6/27 19:01, Jeff Layton wrote:
> > On Wed, 2024-05-15 at 20:51 +0800, libaokun@huaweicloud.com wrote:
> > > From: Baokun Li <libaokun1@huawei.com>
> > >
> > > Because after an object is dropped, requests for that object are
> > > useless,
> > > flush them to avoid causing other problems.
> > >
> > > This prepares for the later addition of cancel_work_sync(). After the
> > > reopen requests is generated, flush it to avoid cancel_work_sync()
> > > blocking by waiting for daemon to complete the reopen requests.
> > >
> > > Signed-off-by: Baokun Li <libaokun1@huawei.com>
> > > ---
> > > fs/cachefiles/ondemand.c | 19 +++++++++++++++++++
> > > 1 file changed, 19 insertions(+)
> > >
> > > diff --git a/fs/cachefiles/ondemand.c b/fs/cachefiles/ondemand.c
> > > index 73da4d4eaa9b..d24bff43499b 100644
> > > --- a/fs/cachefiles/ondemand.c
> > > +++ b/fs/cachefiles/ondemand.c
> > > @@ -564,12 +564,31 @@ int cachefiles_ondemand_init_object(struct
> > > cachefiles_object *object)
> > > void cachefiles_ondemand_clean_object(struct cachefiles_object
> > > *object)
> > > {
> > > + unsigned long index;
> > > + struct cachefiles_req *req;
> > > + struct cachefiles_cache *cache;
> > > +
> > > if (!object->ondemand)
> > > return;
> > > cachefiles_ondemand_send_req(object, CACHEFILES_OP_CLOSE, 0,
> > > cachefiles_ondemand_init_close_req, NULL);
> > > +
> > > + if (!object->ondemand->ondemand_id)
> > > + return;
> > > +
> > > + /* Flush all requests for the object that is being dropped.
> > > */
> > I wouldn't call this a "Flush". In the context of writeback, that
> > usually means that we're writing out pages now in order to do something
> > else. In this case, it looks like you're more canceling these requests
> > since you're marking them with an error and declaring them complete.
> Makes sense, I'll update 'flush' to 'cancel' in the comment and subject.
>
> I am not a native speaker of English, so some of the expressions may
> not be accurate, thank you for correcting me.
Can you please resend all patch series that we're supposed to take for
this cycle, please?
next prev parent reply other threads:[~2024-06-27 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 12:51 [PATCH v2 0/5] cachefiles: some bugfixes for clean object/send req/poll libaokun
2024-05-15 12:51 ` [PATCH v2 1/5] cachefiles: stop sending new request when dropping object libaokun
2024-05-15 12:51 ` [PATCH v2 2/5] cachefiles: flush all requests for the object that is being dropped libaokun
2024-06-27 11:01 ` Jeff Layton
2024-06-27 11:20 ` Baokun Li
2024-06-27 15:18 ` Christian Brauner [this message]
2024-06-28 1:09 ` Baokun Li
2024-05-15 12:51 ` [PATCH v2 3/5] cachefiles: flush ondemand_object_worker during clean object libaokun
2024-05-15 12:51 ` [PATCH v2 4/5] cachefiles: cyclic allocation of msg_id to avoid reuse libaokun
2024-05-19 11:11 ` Jeff Layton
2024-05-20 4:06 ` Baokun Li
2024-05-20 10:04 ` Jeff Layton
2024-05-20 12:42 ` Baokun Li
2024-05-20 12:54 ` Gao Xiang
2024-05-20 13:24 ` Baokun Li
2024-05-20 14:56 ` Gao Xiang
2024-05-21 2:36 ` Baokun Li
2024-05-21 2:53 ` Gao Xiang
2024-05-20 13:24 ` Jeff Layton
2024-05-15 12:51 ` [PATCH v2 5/5] cachefiles: add missing lock protection when polling libaokun
2024-06-26 3:04 ` [PATCH v2 0/5] cachefiles: some bugfixes for clean object/send req/poll Baokun Li
2024-06-26 3:28 ` Gao Xiang
2024-06-27 1:49 ` Baokun Li
2024-06-27 2:08 ` Gao Xiang
2024-06-27 2:18 ` Baokun Li
2024-06-27 11:03 ` Jeff Layton
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=20240627-beizeiten-hecht-0efad69e0e38@brauner \
--to=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=houtao1@huawei.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=jlayton@kernel.org \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=wozizhi@huawei.com \
--cc=yangerkun@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhujia.zj@bytedance.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
all inboxes | Powered by JetHome®