On Fri, Dec 07, 2018 at 11:23:26PM +0530, Naresh Kamboju wrote:
On Fri, 7 Dec 2018 at 21:21, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Fri, Dec 07, 2018 at 03:34:24PM +0000, Ben Hutchings wrote:
On Fri, 2018-12-07 at 15:41 +0100, Greg Kroah-Hartman wrote:
On Fri, Dec 07, 2018 at 02:40:26PM +0530, Naresh Kamboju wrote:
On Thu, 6 Dec 2018 at 20:15, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 4.9.144 release. There are 101 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat Dec 8 14:29:43 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.144-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y and the diffstat can be found below.
thanks,
greg k-h
Mike Kravetz mike.kravetz@oracle.com hugetlbfs: check for pgoff value overflow
Mike Kravetz mike.kravetz@oracle.com hugetlbfs: fix offset overflow in hugetlbfs mmap
Mike Kravetz mike.kravetz@oracle.com mm/hugetlb.c: don't call region_abort if region_chg fails
Results from Linaro’s test farm. Regressions detected on arm32 and i386.
truncate_above_4GB (2M: 32): FAIL mmap() offset 4GB: Invalid argument
Can this be tracked down to a commit in this tree that caused this regression?
The test failure is part of a hugetlb test group, so one of the above is responsible.
Ah, I missed this fix (it's already in 4.14-stable:
commit 5df63c2a149ae65a9ec239e7c2af44efa6f79beb Author: Mike Kravetz mike.kravetz@oracle.com Date: Thu Apr 5 16:18:21 2018 -0700
hugetlbfs: fix bug in pgoff overflow checking
Ben.
Thanks for this, I've queued this up and pushed out a -rc2.
Naresh, can you see if this fixes the issue for you or not?
Yes This test getting pass on -rc2 on all devices arm64, arm32, x86_64 and i386. truncate_above_4GB (2M: 32): PASS
Wonderful, thanks for testing and catching this and letting me know.
greg k-h