linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	linux-mm@kvack.org
Subject: [PATCH] tmpfs: change shmem_mapping() to test shmem_aops
Date: Mon, 5 Dec 2016 21:52:36 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.1612052148530.13021@eggly.anvils> (raw)

Callers of shmem_mapping() are interested in whether the mapping is
swap backed - except for uprobes, which is interested in whether it
should use shmem_read_mapping_page().  All these callers are better
served by a shmem_mapping() which checks for shmem_aops, than the
current version which goes through several indirections to find where
the inode lives - and has the surprising effect that a private mmap of
/dev/zero satisfies both vma_is_anonymous() and shmem_mapping(), when
that device node is on devtmpfs.  I don't think anything in the tree
suffers from that surprise, but it caught me out, and is better fixed.

Signed-off-by: Hugh Dickins <hughd@google.com>
---

 mm/shmem.c |    5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

--- 4.9-rc8/mm/shmem.c	2016-11-13 11:44:43.052622519 -0800
+++ linux/mm/shmem.c	2016-12-05 18:54:25.348596732 -0800
@@ -2131,10 +2131,7 @@ static struct inode *shmem_get_inode(str
 
 bool shmem_mapping(struct address_space *mapping)
 {
-	if (!mapping->host)
-		return false;
-
-	return mapping->host->i_sb->s_op == &shmem_ops;
+	return mapping->a_ops == &shmem_aops;
 }
 
 #ifdef CONFIG_TMPFS

--
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>

             reply	other threads:[~2016-12-06  5:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06  5:52 Hugh Dickins [this message]
2016-12-14 21:15 ` Johannes Weiner

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=alpine.LSU.2.11.1612052148530.13021@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.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