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 2/6] shmem: rename functions that are memfd-related
Date: Wed, 1 Nov 2017 16:01:30 -0700 [thread overview]
Message-ID: <c884ed14-cb4e-fa04-e5be-5a732e64f988@oracle.com> (raw)
In-Reply-To: <20171031184052.25253-3-marcandre.lureau@redhat.com>
On 10/31/2017 11:40 AM, Marc-AndrA(C) Lureau wrote:
> Those functions are called for memfd files, backed by shmem or
> hugetlb (the next patches will handle hugetlb).
>
> Signed-off-by: Marc-AndrA(C) Lureau <marcandre.lureau@redhat.com>
> ---
> fs/fcntl.c | 2 +-
> include/linux/shmem_fs.h | 4 ++--
> mm/shmem.c | 10 +++++-----
> 3 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/fs/fcntl.c b/fs/fcntl.c
> index 448a1119f0be..752c23743616 100644
> --- a/fs/fcntl.c
> +++ b/fs/fcntl.c
> @@ -417,7 +417,7 @@ static long do_fcntl(int fd, unsigned int cmd, unsigned long arg,
> break;
> case F_ADD_SEALS:
> case F_GET_SEALS:
> - err = shmem_fcntl(filp, cmd, arg);
> + err = memfd_fcntl(filp, cmd, arg);
> break;
> case F_GET_RW_HINT:
> case F_SET_RW_HINT:
> diff --git a/include/linux/shmem_fs.h b/include/linux/shmem_fs.h
> index 557d0c3b6eca..0dac8c0f4aa4 100644
> --- a/include/linux/shmem_fs.h
> +++ b/include/linux/shmem_fs.h
> @@ -109,11 +109,11 @@ extern void shmem_uncharge(struct inode *inode, long pages);
>
> #ifdef CONFIG_TMPFS
>
> -extern long shmem_fcntl(struct file *file, unsigned int cmd, unsigned long arg);
> +extern long memfd_fcntl(struct file *file, unsigned int cmd, unsigned long arg);
>
> #else
>
> -static inline long shmem_fcntl(struct file *f, unsigned int c, unsigned long a)
> +static inline long memfd_fcntl(struct file *f, unsigned int c, unsigned long a)
> {
> return -EINVAL;
> }
Do we want memfd_fcntl() to work for hugetlbfs if CONFIG_TMPFS is not
defined? I admit that having CONFIG_HUGETLBFS defined without CONFIG_TMPFS
is unlikely, but I think possible. Based on the above #ifdef/#else, I
think hugetlbfs seals will not work if CONFIG_TMPFS is not defined.
--
Mike Kravetz
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 37260c5e12fa..b7811979611f 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)
>
> -static int shmem_add_seals(struct file *file, unsigned int seals)
> +static int memfd_add_seals(struct file *file, unsigned int seals)
> {
> struct inode *inode = file_inode(file);
> struct shmem_inode_info *info = SHMEM_I(inode);
> @@ -2792,7 +2792,7 @@ static int shmem_add_seals(struct file *file, unsigned int seals)
> return error;
> }
>
> -static int shmem_get_seals(struct file *file)
> +static int memfd_get_seals(struct file *file)
> {
> if (file->f_op != &shmem_file_operations)
> return -EINVAL;
> @@ -2800,7 +2800,7 @@ static int shmem_get_seals(struct file *file)
> return SHMEM_I(file_inode(file))->seals;
> }
>
> -long shmem_fcntl(struct file *file, unsigned int cmd, unsigned long arg)
> +long memfd_fcntl(struct file *file, unsigned int cmd, unsigned long arg)
> {
> long error;
>
> @@ -2810,10 +2810,10 @@ long shmem_fcntl(struct file *file, unsigned int cmd, unsigned long arg)
> if (arg > UINT_MAX)
> return -EINVAL;
>
> - error = shmem_add_seals(file, arg);
> + error = memfd_add_seals(file, arg);
> break;
> case F_GET_SEALS:
> - error = shmem_get_seals(file);
> + error = memfd_get_seals(file);
> break;
> default:
> error = -EINVAL;
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-01 23:01 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
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 [this message]
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=c884ed14-cb4e-fa04-e5be-5a732e64f988@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