public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Huang <nickhuang@synology.com>
To: bfields@fieldses.org, chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org,
	Yu Hsiang Huang <nickhuang@synology.com>,
	Bing Jing Chang <bingjingc@synology.com>,
	Robbie Ko <robbieko@synology.com>
Subject: [PATCH] nfsd: Prevent truncation of an unlinked inode from blocking access to its directory
Date: Fri, 14 May 2021 11:58:29 +0800	[thread overview]
Message-ID: <20210514035829.5230-1-nickhuang@synology.com> (raw)

From: Yu Hsiang Huang <nickhuang@synology.com>

Truncation of an unlinked inode may take a long time for I/O waiting, and
it doesn't have to prevent access to the directory. Thus, let truncation
occur outside the directory's mutex, just like do_unlinkat() does.

Signed-off-by: Yu Hsiang Huang <nickhuang@synology.com>
Signed-off-by: Bing Jing Chang <bingjingc@synology.com>
Signed-off-by: Robbie Ko <robbieko@synology.com>
---
 fs/nfsd/vfs.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index 15adf1f6ab21..39948f130712 100644
--- a/fs/nfsd/vfs.c
+++ b/fs/nfsd/vfs.c
@@ -1859,6 +1859,7 @@ nfsd_unlink(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
 {
 	struct dentry	*dentry, *rdentry;
 	struct inode	*dirp;
+	struct inode	*rinode;
 	__be32		err;
 	int		host_err;
 
@@ -1887,6 +1888,8 @@ nfsd_unlink(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
 		host_err = -ENOENT;
 		goto out_drop_write;
 	}
+	rinode = d_inode(rdentry);
+	ihold(rinode);
 
 	if (!type)
 		type = d_inode(rdentry)->i_mode & S_IFMT;
@@ -1902,6 +1905,8 @@ nfsd_unlink(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
 	if (!host_err)
 		host_err = commit_metadata(fhp);
 	dput(rdentry);
+	fh_unlock(fhp);
+	iput(rinode);    /* truncate the inode here */
 
 out_drop_write:
 	fh_drop_write(fhp);
-- 
2.25.1


             reply	other threads:[~2021-05-14  3:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  3:58 Nick Huang [this message]
2021-05-14 15:09 ` [PATCH] nfsd: Prevent truncation of an unlinked inode from blocking access to its directory J. Bruce Fields
2021-05-14 15:46 ` Trond Myklebust
2021-05-15  7:02   ` Christoph Hellwig
2021-05-17 18:56     ` bfields
2021-05-18  7:33       ` Christoph Hellwig
2021-05-18 17:53     ` Trond Myklebust
2021-05-18 18:21       ` bfields
2021-05-18 18:36         ` Trond Myklebust
2021-05-18 18:39           ` bfields
2021-05-18 21:06   ` bfields

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=20210514035829.5230-1-nickhuang@synology.com \
    --to=nickhuang@synology.com \
    --cc=bfields@fieldses.org \
    --cc=bingjingc@synology.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=robbieko@synology.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