From: Anders Roxell <anders.roxell@linaro.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Yisheng Xie <xieyisheng1@huawei.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Nic Losby <blurbdust@gmail.com>, Dan Rue <dan.rue@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] hugetlbfs: fix bug in pgoff overflow checking
Date: Mon, 2 Apr 2018 18:21:01 +0200 [thread overview]
Message-ID: <CADYN=9+FzfFt8kKjw-hnHx7CdPbTsH0OsNs1TAGHa6Hi7ndbZQ@mail.gmail.com> (raw)
In-Reply-To: <20180330145402.5053-1-mike.kravetz@oracle.com>
On 30 March 2018 at 16:54, Mike Kravetz <mike.kravetz@oracle.com> wrote:
> This is a fix for a regression in 32 bit kernels caused by an
> invalid check for pgoff overflow in hugetlbfs mmap setup. The
> check incorrectly specified that the size of a loff_t was the
> same as the size of a long. The regression prevents mapping
> hugetlbfs files at offsets greater than 4GB on 32 bit kernels.
>
> On 32 bit kernels conversion from a page based unsigned long can
> not overflow a loff_t byte offset. Therefore, skip this check
> if sizeof(unsigned long) != sizeof(loff_t).
>
> Fixes: 63489f8e8211 ("hugetlbfs: check for pgoff value overflow")
> Cc: <stable@vger.kernel.org>
> Reported-by: Dan Rue <dan.rue@linaro.org>
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
Tested-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> fs/hugetlbfs/inode.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> index b9a254dcc0e7..d508c7844681 100644
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -138,10 +138,14 @@ static int hugetlbfs_file_mmap(struct file *file, struct vm_area_struct *vma)
>
> /*
> * page based offset in vm_pgoff could be sufficiently large to
> - * overflow a (l)off_t when converted to byte offset.
> + * overflow a loff_t when converted to byte offset. This can
> + * only happen on architectures where sizeof(loff_t) ==
> + * sizeof(unsigned long). So, only check in those instances.
> */
> - if (vma->vm_pgoff & PGOFF_LOFFT_MAX)
> - return -EINVAL;
> + if (sizeof(unsigned long) == sizeof(loff_t)) {
> + if (vma->vm_pgoff & PGOFF_LOFFT_MAX)
> + return -EINVAL;
> + }
>
> /* must be huge page aligned */
> if (vma->vm_pgoff & (~huge_page_mask(h) >> PAGE_SHIFT))
> --
> 2.13.6
>
prev parent reply other threads:[~2018-04-02 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 4:16 [PATCH 0/1] fix regression in hugetlbfs " Mike Kravetz
2018-03-29 4:16 ` [PATCH 1/1] hugetlbfs: fix bug in pgoff " Mike Kravetz
2018-03-29 16:00 ` kbuild test robot
2018-03-29 20:42 ` [PATCH 0/1] fix regression in hugetlbfs " Mike Kravetz
2018-03-30 14:54 ` [PATCH v2] hugetlbfs: fix bug in pgoff " Mike Kravetz
2018-04-02 16:21 ` Anders Roxell [this message]
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='CADYN=9+FzfFt8kKjw-hnHx7CdPbTsH0OsNs1TAGHa6Hi7ndbZQ@mail.gmail.com' \
--to=anders.roxell@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=blurbdust@gmail.com \
--cc=dan.rue@linaro.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