From: Yicong Yang <yangyicong@hisilicon.com>
To: <viro@zeniv.linux.org.uk>, <linux-fsdevel@vger.kernel.org>
Cc: <hch@lst.de>, <linux-kernel@vger.kernel.org>,
<prime.zeng@huawei.com>, <linuxarm@huawei.com>,
<yangyicong@hisilicon.com>
Subject: [PATCH] fs: export vfs_stat() and vfs_fstatat()
Date: Thu, 26 Nov 2020 15:15:48 +0800 [thread overview]
Message-ID: <1606374948-38713-1-git-send-email-yangyicong@hisilicon.com> (raw)
The public function vfs_stat() and vfs_fstatat() are
unexported after moving out of line in
commit 09f1bde4017e ("fs: move vfs_fstatat out of line"),
which will prevent the using in kernel modules.
So make them exported.
Fixes: 09f1bde4017e ("fs: move vfs_fstatat out of line")
Reported-by: Yang Shen <shenyang39@huawei.com>
Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
---
fs/stat.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/stat.c b/fs/stat.c
index dacecdd..7d690c6 100644
--- a/fs/stat.c
+++ b/fs/stat.c
@@ -147,6 +147,7 @@ int vfs_fstat(int fd, struct kstat *stat)
fdput(f);
return error;
}
+EXPORT_SYMBOL(vfs_fstat);
/**
* vfs_statx - Get basic and extra attributes by filename
@@ -207,6 +208,7 @@ int vfs_fstatat(int dfd, const char __user *filename,
return vfs_statx(dfd, filename, flags | AT_NO_AUTOMOUNT,
stat, STATX_BASIC_STATS);
}
+EXPORT_SYMBOL(vfs_fstatat);
#ifdef __ARCH_WANT_OLD_STAT
--
2.8.1
next reply other threads:[~2020-11-26 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 7:15 Yicong Yang [this message]
2020-11-26 7:18 ` [PATCH] fs: export vfs_stat() and vfs_fstatat() Christoph Hellwig
2020-11-26 9:08 ` Yicong Yang
2020-11-26 9:15 ` Christoph Hellwig
2020-11-26 9:48 ` Yicong Yang
2020-11-26 9:50 ` Christoph Hellwig
2020-11-26 10:44 ` Yicong Yang
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=1606374948-38713-1-git-send-email-yangyicong@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@huawei.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).