Re: [PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

2018-04-02 Thread Anders Roxell
On 30 March 2018 at 16:54, Mike Kravetz 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.

Re: [PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

2018-04-02 Thread Anders Roxell
On 30 March 2018 at 16:54, Mike Kravetz 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

[PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

2018-03-30 Thread Mike Kravetz
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

[PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

2018-03-30 Thread Mike Kravetz
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