From: Khalid Aziz <khalid.aziz@oracle.com>
To: Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: "Matthew Wilcox" <willy@infradead.org>,
"Hugh Dickins" <hughd@google.com>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"David Herrmann" <dh.herrmann@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 2/3] mm/shmem: update file sealing comments and file checking
Date: Tue, 10 Apr 2018 10:54:21 -0600 [thread overview]
Message-ID: <e710688c-1086-f9e4-6589-e4b5641ae30c@oracle.com> (raw)
In-Reply-To: <20180409230505.18953-3-mike.kravetz@oracle.com>
On 04/09/2018 05:05 PM, Mike Kravetz wrote:
> In preparation for memfd code restucture, update comments dealing
> with file sealing to indicate that tmpfs and hugetlbfs are the
> supported filesystems. Also, change file pointer checks in
> memfd_file_seals_ptr to use defined routines instead of directly
> referencing file_operation structs.
>
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
> ---
> mm/shmem.c | 29 +++++++++++++++--------------
> 1 file changed, 15 insertions(+), 14 deletions(-)
>
Reviewed-by: Khalid Aziz <khalid.aziz@oracle.com>
next prev parent reply other threads:[~2018-04-10 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 23:05 [PATCH v3 0/3] restructure memfd code Mike Kravetz
2018-04-09 23:05 ` [PATCH v3 1/3] mm/shmem: add __rcu annotations and properly deref radix entry Mike Kravetz
2018-04-09 23:05 ` [PATCH v3 2/3] mm/shmem: update file sealing comments and file checking Mike Kravetz
2018-04-10 16:54 ` Khalid Aziz [this message]
2018-04-10 23:51 ` Mike Kravetz
2018-04-09 23:05 ` [PATCH v3 3/3] mm: restructure memfd code Mike Kravetz
2018-04-10 1:41 ` Matthew Wilcox
2018-04-10 3:03 ` Mike Kravetz
2018-04-10 23:55 ` Mike Kravetz
2018-04-10 16:55 ` Khalid Aziz
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=e710688c-1086-f9e4-6589-e4b5641ae30c@oracle.com \
--to=khalid.aziz@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcandre.lureau@gmail.com \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=willy@infradead.org \
/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