From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
Michal Hocko <mhocko@kernel.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Nic Losby <blurbdust@gmail.com>,
Yisheng Xie <xieyisheng1@huawei.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] hugetlbfs: check for pgoff value overflow
Date: Thu, 8 Mar 2018 17:05:11 -0800 [thread overview]
Message-ID: <20180308170511.c16fc731523ff49f1981f89d@linux-foundation.org> (raw)
In-Reply-To: <20180309002726.7248-1-mike.kravetz@oracle.com>
On Thu, 8 Mar 2018 16:27:26 -0800 Mike Kravetz <mike.kravetz@oracle.com> wrote:
> A vma with vm_pgoff large enough to overflow a loff_t type when
> converted to a byte offset can be passed via the remap_file_pages
> system call. The hugetlbfs mmap routine uses the byte offset to
> calculate reservations and file size.
>
> A sequence such as:
> mmap(0x20a00000, 0x600000, 0, 0x66033, -1, 0);
> remap_file_pages(0x20a00000, 0x600000, 0, 0x20000000000000, 0);
> will result in the following when task exits/file closed,
> kernel BUG at mm/hugetlb.c:749!
> Call Trace:
> hugetlbfs_evict_inode+0x2f/0x40
> evict+0xcb/0x190
> __dentry_kill+0xcb/0x150
> __fput+0x164/0x1e0
> task_work_run+0x84/0xa0
> exit_to_usermode_loop+0x7d/0x80
> do_syscall_64+0x18b/0x190
> entry_SYSCALL_64_after_hwframe+0x3d/0xa2
>
> The overflowed pgoff value causes hugetlbfs to try to set up a
> mapping with a negative range (end < start) that leaves invalid
> state which causes the BUG.
>
> The previous overflow fix to this code was incomplete and did not
> take the remap_file_pages system call into account.
>
> ...
>
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4374,6 +4374,12 @@ int hugetlb_reserve_pages(struct inode *inode,
> struct resv_map *resv_map;
> long gbl_reserve;
>
> + /* This should never happen */
> + if (from > to) {
> + VM_WARN(1, "%s called with a negative range\n", __func__);
> + return -EINVAL;
> + }
This is tidier, and that comment is a bit too obvious to live ;)
--- a/mm/hugetlb.c~hugetlbfs-check-for-pgoff-value-overflow-v3-fix
+++ a/mm/hugetlb.c
@@ -18,6 +18,7 @@
#include <linux/bootmem.h>
#include <linux/sysfs.h>
#include <linux/slab.h>
+#include <linux/mmdebug.h>
#include <linux/sched/signal.h>
#include <linux/rmap.h>
#include <linux/string_helpers.h>
@@ -4374,11 +4375,8 @@ int hugetlb_reserve_pages(struct inode *
struct resv_map *resv_map;
long gbl_reserve;
- /* This should never happen */
- if (from > to) {
- VM_WARN(1, "%s called with a negative range\n", __func__);
+ if (VM_WARN(from > to, "%s called with a negative range\n", __func__))
return -EINVAL;
- }
/*
* Only apply hugepage reservation if asked. At fault time, an
next prev parent reply other threads:[~2018-03-09 1:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199037-27@https.bugzilla.kernel.org/>
2018-03-06 21:31 ` [Bug 199037] New: Kernel bug at mm/hugetlb.c:741 Andrew Morton
2018-03-06 21:46 ` Mike Kravetz
2018-03-07 0:31 ` Mike Kravetz
2018-03-07 2:49 ` Nic Losby
2018-03-07 4:19 ` Mike Kravetz
2018-03-07 16:39 ` Mike Kravetz
2018-03-07 23:59 ` [PATCH] hugetlbfs: check for pgoff value overflow Mike Kravetz
2018-03-08 0:57 ` Nic Losby
2018-03-08 1:35 ` Yisheng Xie
2018-03-08 4:25 ` Mike Kravetz
2018-03-08 21:03 ` Mike Kravetz
2018-03-08 21:05 ` [PATCH v2] " Mike Kravetz
2018-03-08 22:15 ` Andrew Morton
2018-03-08 23:37 ` Mike Kravetz
2018-03-08 23:53 ` Andrew Morton
2018-03-09 0:27 ` [PATCH v3] " Mike Kravetz
2018-03-09 1:05 ` Andrew Morton [this message]
2018-03-16 10:17 ` Michal Hocko
2018-03-16 16:19 ` Mike Kravetz
2018-03-16 16:53 ` Michal Hocko
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=20180308170511.c16fc731523ff49f1981f89d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=blurbdust@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=stable@vger.kernel.org \
--cc=xieyisheng1@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