From: Li Lingfeng <lilingfeng3@huawei.com>
To: <chuck.lever@oracle.com>, <jlayton@kernel.org>, <neilb@suse.de>,
<okorniev@redhat.com>, <kolga@netapp.com>, <Dai.Ngo@oracle.com>,
<tom@talpey.com>, <trondmy@hammerspace.com>,
<linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <yukuai1@huaweicloud.com>, <houtao1@huawei.com>,
<yi.zhang@huawei.com>, <yangerkun@huawei.com>,
<lilingfeng@huaweicloud.com>, <lilingfeng3@huawei.com>
Subject: [PATCH 2/2] nfsd: remove the redundant mapping of nfserr_mlink
Date: Sun, 26 Jan 2025 17:50:45 +0800 [thread overview]
Message-ID: <20250126095045.738902-3-lilingfeng3@huawei.com> (raw)
In-Reply-To: <20250126095045.738902-1-lilingfeng3@huawei.com>
There two mappings of nfserr_mlink in nfs_errtbl.
Remove one of them.
Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
---
fs/nfsd/vfs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index 0f727010b8cb..42039cff2124 100644
--- a/fs/nfsd/vfs.c
+++ b/fs/nfsd/vfs.c
@@ -71,7 +71,6 @@ nfserrno (int errno)
{ nfserr_acces, -EACCES },
{ nfserr_exist, -EEXIST },
{ nfserr_xdev, -EXDEV },
- { nfserr_mlink, -EMLINK },
{ nfserr_nodev, -ENODEV },
{ nfserr_notdir, -ENOTDIR },
{ nfserr_isdir, -EISDIR },
--
2.31.1
next prev parent reply other threads:[~2025-01-26 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 9:50 [PATCH 0/2] nfsd: add a new mapping and remove the redundant one Li Lingfeng
2025-01-26 9:50 ` [PATCH 1/2] nfsd: map the ELOOP to nfserr_symlink to avoid warning Li Lingfeng
2025-01-26 17:27 ` Chuck Lever
2025-01-27 2:33 ` Li Lingfeng
2025-01-27 13:28 ` Chuck Lever
2025-02-05 1:53 ` Li Lingfeng
2025-02-05 14:54 ` Chuck Lever
2025-02-06 1:09 ` NeilBrown
2025-01-26 9:50 ` Li Lingfeng [this message]
2025-01-26 19:01 ` [PATCH 0/2] nfsd: add a new mapping and remove the redundant one cel
2025-01-27 14:52 ` 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=20250126095045.738902-3-lilingfeng3@huawei.com \
--to=lilingfeng3@huawei.com \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=houtao1@huawei.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=lilingfeng@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@hammerspace.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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