From: Luis Chamberlain <mcgrof@kernel.org>
To: viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org,
rafael@kernel.org, ebiederm@xmission.com, jeyu@kernel.org,
jmorris@namei.org, keescook@chromium.org, paul@paul-moore.com,
stephen.smalley.work@gmail.com, eparis@parisplace.org,
nayna@linux.ibm.com, zohar@linux.ibm.com
Cc: scott.branden@broadcom.com, dan.carpenter@oracle.com,
skhan@linuxfoundation.org, geert@linux-m68k.org,
tglx@linutronix.de, bauerman@linux.ibm.com, dhowells@redhat.com,
linux-integrity@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kexec@lists.infradead.org, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 1/3] fs: unexport kernel_read_file()
Date: Wed, 13 May 2020 15:21:06 +0000 [thread overview]
Message-ID: <20200513152108.25669-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20200513152108.25669-1-mcgrof@kernel.org>
There are no modular uses of kernel_read_file(), so just unexport it.
Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
fs/exec.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/exec.c b/fs/exec.c
index 23dc2b45d590..9791b9eef9ce 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -988,7 +988,6 @@ int kernel_read_file(struct file *file, void **buf, loff_t *size,
allow_write_access(file);
return ret;
}
-EXPORT_SYMBOL_GPL(kernel_read_file);
int kernel_read_file_from_path(const char *path, void **buf, loff_t *size,
loff_t max_size, enum kernel_read_file_id id)
--
2.26.2
next prev parent reply other threads:[~2020-05-13 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 15:21 [PATCH 0/3] fs: reduce export usage of kerne_read*() calls Luis Chamberlain
2020-05-13 15:21 ` Luis Chamberlain [this message]
2020-05-13 15:21 ` [PATCH 2/3] security: add symbol namespace for reading file data Luis Chamberlain
2020-05-13 15:40 ` Eric W. Biederman
2020-05-13 16:09 ` Greg KH
2020-05-13 16:16 ` Luis Chamberlain
2020-05-13 16:26 ` Greg KH
2020-05-13 18:07 ` Josh Triplett
2020-05-13 15:21 ` [PATCH 3/3] fs: move kernel_read*() calls to its own symbol namespace Luis Chamberlain
2020-05-13 16:08 ` Greg KH
2020-05-13 18:17 ` [PATCH 0/3] fs: reduce export usage of kerne_read*() calls Christoph Hellwig
2020-05-15 21:29 ` Luis Chamberlain
2020-05-18 6:22 ` Christoph Hellwig
2020-05-18 12:37 ` Mimi Zohar
2020-05-18 15:21 ` Kees Cook
2020-07-29 1:20 ` Luis Chamberlain
2020-05-22 22:24 ` Scott Branden
2020-05-22 23:04 ` Kees Cook
2020-05-22 23:25 ` Scott Branden
2020-05-24 2:52 ` Mimi Zohar
2020-06-05 18:15 ` Scott Branden
2020-06-05 18:37 ` Mimi Zohar
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=20200513152108.25669-2-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=bauerman@linux.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nayna@linux.ibm.com \
--cc=paul@paul-moore.com \
--cc=rafael@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=selinux@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).