From: Mike Kravetz <mike.kravetz@oracle.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: aarcange@redhat.com, hughd@google.com, nyc@holomorphy.com
Subject: Re: [PATCH 1/6] shmem: unexport shmem_add_seals()/shmem_get_seals()
Date: Wed, 1 Nov 2017 15:50:23 -0700 [thread overview]
Message-ID: <bc39fa5e-e11f-6960-a338-528e689a7acb@oracle.com> (raw)
In-Reply-To: <20171031184052.25253-2-marcandre.lureau@redhat.com>
On 10/31/2017 11:40 AM, Marc-André Lureau wrote:
> The functions are called through shmem_fcntl() only.
And no danger in removing the EXPORTs as the routines only work
with shmem file structs.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
--
Mike Kravetz
> ---
> include/linux/shmem_fs.h | 2 --
> mm/shmem.c | 6 ++----
> 2 files changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/include/linux/shmem_fs.h b/include/linux/shmem_fs.h
> index b6c3540e07bc..557d0c3b6eca 100644
> --- a/include/linux/shmem_fs.h
> +++ b/include/linux/shmem_fs.h
> @@ -109,8 +109,6 @@ extern void shmem_uncharge(struct inode *inode, long pages);
>
> #ifdef CONFIG_TMPFS
>
> -extern int shmem_add_seals(struct file *file, unsigned int seals);
> -extern int shmem_get_seals(struct file *file);
> extern long shmem_fcntl(struct file *file, unsigned int cmd, unsigned long arg);
>
> #else
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 07a1d22807be..37260c5e12fa 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -2722,7 +2722,7 @@ static int shmem_wait_for_pins(struct address_space *mapping)
> F_SEAL_GROW | \
> F_SEAL_WRITE)
>
> -int shmem_add_seals(struct file *file, unsigned int seals)
> +static int shmem_add_seals(struct file *file, unsigned int seals)
> {
> struct inode *inode = file_inode(file);
> struct shmem_inode_info *info = SHMEM_I(inode);
> @@ -2791,16 +2791,14 @@ int shmem_add_seals(struct file *file, unsigned int seals)
> inode_unlock(inode);
> return error;
> }
> -EXPORT_SYMBOL_GPL(shmem_add_seals);
>
> -int shmem_get_seals(struct file *file)
> +static int shmem_get_seals(struct file *file)
> {
> if (file->f_op != &shmem_file_operations)
> return -EINVAL;
>
> return SHMEM_I(file_inode(file))->seals;
> }
> -EXPORT_SYMBOL_GPL(shmem_get_seals);
>
> long shmem_fcntl(struct file *file, unsigned int cmd, unsigned long arg)
> {
>
next prev parent reply other threads:[~2017-11-01 22:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 18:40 [PATCH 0/6] memfd: add sealing to hugetlb-backed memory Marc-André Lureau
2017-10-31 18:40 ` [PATCH 1/6] shmem: unexport shmem_add_seals()/shmem_get_seals() Marc-André Lureau
2017-11-01 22:50 ` Mike Kravetz [this message]
2017-10-31 18:40 ` [PATCH 2/6] shmem: rename functions that are memfd-related Marc-André Lureau
2017-11-01 23:01 ` Mike Kravetz
2017-11-03 16:02 ` Marc-André Lureau
2017-11-03 16:22 ` Mike Kravetz
2017-11-03 16:36 ` Marc-André Lureau
2017-11-03 18:07 ` Mike Kravetz
2017-10-31 18:40 ` [PATCH 3/6] hugetlb: expose hugetlbfs_inode_info in header Marc-André Lureau
2017-11-01 23:20 ` Mike Kravetz
2017-11-03 16:14 ` Marc-André Lureau
2017-11-03 16:23 ` Mike Kravetz
2017-10-31 18:40 ` [PATCH 4/6] hugetlbfs: implement memfd sealing Marc-André Lureau
2017-11-01 23:44 ` Mike Kravetz
2017-11-03 17:03 ` David Herrmann
2017-11-03 17:12 ` Mike Kravetz
2017-11-03 17:41 ` David Herrmann
2017-11-03 17:56 ` Mike Kravetz
2017-11-03 23:31 ` Mike Kravetz
2017-11-05 12:07 ` David Herrmann
2017-10-31 18:40 ` [PATCH 5/6] shmem: add sealing support to hugetlb-backed memfd Marc-André Lureau
2017-11-02 0:18 ` Mike Kravetz
2017-11-03 16:13 ` Marc-André Lureau
2017-10-31 18:40 ` [PATCH 6/6] memfd-tests: test hugetlbfs sealing Marc-André Lureau
2017-11-03 23:59 ` Mike Kravetz
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=bc39fa5e-e11f-6960-a338-528e689a7acb@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcandre.lureau@redhat.com \
--cc=nyc@holomorphy.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).