From: Dave Hansen <dave.hansen@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Zhong Jiang <zhongjiang@huawei.com>,
Laura Abbott <labbott@fedoraproject.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] mm: huge-vmap: fail gracefully on unexpected huge vmap mappings
Date: Thu, 8 Jun 2017 10:19:52 -0700 [thread overview]
Message-ID: <2f5358b4-b1a7-f51d-ae47-5faa93e1e1d7@intel.com> (raw)
In-Reply-To: <CAKv+Gu9Wp06Nk33CVFr5W51gnsjaRsf0fQJOS4RWbHfRP+KEcg@mail.gmail.com>
On 06/08/2017 04:36 AM, Ard Biesheuvel wrote:
> @@ -287,10 +288,10 @@ struct page *vmalloc_to_page(const void *vmalloc_addr)
> if (p4d_none(*p4d))
> return NULL;
> pud = pud_offset(p4d, addr);
> - if (pud_none(*pud))
> + if (pud_none(*pud) || WARN_ON_ONCE(pud_huge(*pud)))
> return NULL;
> pmd = pmd_offset(pud, addr);
> - if (pmd_none(*pmd))
> + if (pmd_none(*pmd) || WARN_ON_ONCE(pmd_huge(*pmd)))
> return NULL;
Seems sane to me. It might be nice to actually comment this, though, on
why huge vmalloc_to_page() is unsupported.
Also, not a big deal, but I tend to filter out the contents of
WARN_ON_ONCE() when trying to figure out what code does, so I think I'd
rather this be:
WARN_ON_ONCE(pmd_huge(*pmd));
if (pmd_none(*pmd) || pmd_huge(*pmd))
...
But, again, not a big deal.
--
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-06-08 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 11:35 Ard Biesheuvel
2017-06-08 11:36 ` Ard Biesheuvel
2017-06-08 17:19 ` Dave Hansen [this message]
2017-06-08 12:59 ` Mark Rutland
2017-06-08 13:12 ` Ard Biesheuvel
2017-06-08 13:28 ` Mark Rutland
2017-06-08 14:51 ` Ard Biesheuvel
2017-06-08 16:37 ` Mark Rutland
2017-06-09 4:32 ` kbuild test robot
2017-06-09 7:45 ` kbuild test robot
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=2f5358b4-b1a7-f51d-ae47-5faa93e1e1d7@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=labbott@fedoraproject.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=zhongjiang@huawei.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