From: Ashish Sangwan <ashishsangwan2@gmail.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: ashishsangwan2@gmail.com, stable@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] NFS: Fix mode bits and nlink count for v4 referral dirs
Date: Tue, 6 Oct 2020 08:14:56 -0700 [thread overview]
Message-ID: <20201006151456.20875-1-ashishsangwan2@gmail.com> (raw)
Request for mode bits and nlink count in the nfs4_get_referral call
and if server returns them use them instead of hard coded values.
CC: stable@vger.kernel.org
Signed-off-by: Ashish Sangwan <ashishsangwan2@gmail.com>
---
fs/nfs/nfs4proc.c | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 6e95c85fe395..efec05c5f535 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -266,7 +266,9 @@ const u32 nfs4_fs_locations_bitmap[3] = {
| FATTR4_WORD0_FSID
| FATTR4_WORD0_FILEID
| FATTR4_WORD0_FS_LOCATIONS,
- FATTR4_WORD1_OWNER
+ FATTR4_WORD1_MODE
+ | FATTR4_WORD1_NUMLINKS
+ | FATTR4_WORD1_OWNER
| FATTR4_WORD1_OWNER_GROUP
| FATTR4_WORD1_RAWDEV
| FATTR4_WORD1_SPACE_USED
@@ -7594,16 +7596,28 @@ nfs4_listxattr_nfs4_user(struct inode *inode, char *list, size_t list_len)
*/
static void nfs_fixup_referral_attributes(struct nfs_fattr *fattr)
{
+ bool fix_mode = true, fix_nlink = true;
+
if (!(((fattr->valid & NFS_ATTR_FATTR_MOUNTED_ON_FILEID) ||
(fattr->valid & NFS_ATTR_FATTR_FILEID)) &&
(fattr->valid & NFS_ATTR_FATTR_FSID) &&
(fattr->valid & NFS_ATTR_FATTR_V4_LOCATIONS)))
return;
+ if (fattr->valid & NFS_ATTR_FATTR_MODE)
+ fix_mode = false;
+ if (fattr->valid & NFS_ATTR_FATTR_NLINK)
+ fix_nlink = false;
fattr->valid |= NFS_ATTR_FATTR_TYPE | NFS_ATTR_FATTR_MODE |
NFS_ATTR_FATTR_NLINK | NFS_ATTR_FATTR_V4_REFERRAL;
- fattr->mode = S_IFDIR | S_IRUGO | S_IXUGO;
- fattr->nlink = 2;
+
+ if (fix_mode)
+ fattr->mode = S_IFDIR | S_IRUGO | S_IXUGO;
+ else
+ fattr->mode |= S_IFDIR;
+
+ if (fix_nlink)
+ fattr->nlink = 2;
}
static int _nfs4_proc_fs_locations(struct rpc_clnt *client, struct inode *dir,
--
2.22.0
next reply other threads:[~2020-10-06 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 15:14 Ashish Sangwan [this message]
2020-10-14 18:17 ` Trond Myklebust
2020-10-14 19:09 ` Ashish Sangwan
2020-10-15 12:06 ` Trond Myklebust
2020-10-15 13:36 ` Chuck Lever
2020-10-15 13:59 ` Trond Myklebust
2020-10-15 14:08 ` Chuck Lever
2020-10-15 20:15 ` Ashish Sangwan
2020-10-15 14:28 ` Chuck Lever
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=20201006151456.20875-1-ashishsangwan2@gmail.com \
--to=ashishsangwan2@gmail.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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®