Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20181206143011.174892052@linuxfoundation.org>
In-Reply-To: <20181206143011.174892052@linuxfoundation.org>
From:   Naresh Kamboju <naresh.kamboju@linaro.org>
Date:   Fri, 7 Dec 2018 14:40:26 +0530
Message-ID: <CA+G9fYtzxd9a=OVr=Uwcouqikpe2EB_WJyuBhO7BX96mYWJ1NQ@mail.gmail.com>
Subject: Re: [PATCH 4.9 000/101] 4.9.144-stable review
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        mike.kravetz@oracle.com
Cc:     open list <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Guenter Roeck <linux@roeck-us.net>,
        Shuah Khan <shuah@kernel.org>, patches@kernelci.org,
        Ben Hutchings <ben.hutchings@codethink.co.uk>,
        lkft-triage@lists.linaro.org,
        linux- stable <stable@vger.kernel.org>,
        Eric Munson <emunson@mgebm.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.gz
> 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=E2=80=99s test farm.
Regressions detected on arm32 and i386.

truncate_above_4GB (2M: 32): FAIL mmap() offset 4GB: Invalid argument

test case link:
https://github.com/libhugetlbfs/libhugetlbfs/blob/master/tests/truncate_abo=
ve_4GB.c

Full test log links,
https://lkft.validation.linaro.org/scheduler/job/537897#L1373

Summary
------------------------------------------------------------------------

kernel: 4.9.144-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stab=
le-rc.git
git branch: linux-4.9.y
git commit: cf137e4b43737b5c238350d3e22f031c616dd9f9
git describe: v4.9.143-102-gcf137e4b4373
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/bui=
ld/v4.9.143-102-gcf137e4b4373

Regressions (compared to build v4.9.143)
------------------------------------------------------------------------

qemu_arm:
  libhugetlbfs:
    * truncate_above_4GB-2M-32

qemu_i386:
  libhugetlbfs:
    * truncate_above_4GB-4M-32

x15 - arm:
  libhugetlbfs:
    * truncate_above_4GB-2M-32

Test description:
----------------------
https://github.com/libhugetlbfs/libhugetlbfs/blob/master/tests/truncate_abo=
ve_4GB.c

/*
* Test rationale:
*
* At one stage, a misconversion of hugetlb_vmtruncate_list to a
* prio_tree meant that on 32-bit machines, truncates at or above 4GB
* could truncate lower pages, resulting in BUG_ON()s.
*
* WARNING: The offsets and addresses used within are specifically
* calculated to trigger the bug as it existed. Don't mess with them
* unless you *really* know what you're doing.
*
* The kernel bug in question was fixed with commit
* 856fc29505556cf263f3dcda2533cf3766c14ab6.
*/

--=20
Linaro LKFT
https://lkft.linaro.org