From: "Zhou Jifeng" <zhoujifeng@kylinsec.com.cn>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Where Is Dirty Data Flushed During NFSv4 Delegation Recall?
Date: Thu, 11 Sep 2025 10:30:02 +0800 [thread overview]
Message-ID: <tencent_6A84D2E177043C91217A1CF6@qq.com> (raw)
Hello everyone, I have a question that has been bothering me for a long
time. I would like to ask a familiar friend to help explain it. In the NFSv4
protocol, it is clearly defined that during the delegation RECALL
processing, the client needs to write the modified cache to the server
side. However, throughout the process, I have not found the code for
flushing dirty data in the kernel NFS client. I have repeatedly reviewed
the code logic of nfs4_callback_recall and nfs4_state_manager, but still
cannot understand where the dirty data is flushed.
My question is: When the client is handling the RECALL operation, where
does the process of flushing the dirty data take place?
Best regards
next reply other threads:[~2025-09-11 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 2:30 Zhou Jifeng [this message]
2025-09-11 14:29 ` Where Is Dirty Data Flushed During NFSv4 Delegation Recall? Trond Myklebust
2025-09-15 11:23 ` Zhou Jifeng
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=tencent_6A84D2E177043C91217A1CF6@qq.com \
--to=zhoujifeng@kylinsec.com.cn \
--cc=linux-nfs@vger.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