From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933541AbdCKBEi (ORCPT ); Fri, 10 Mar 2017 20:04:38 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:58466 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932687AbdCKBEc (ORCPT ); Fri, 10 Mar 2017 20:04:32 -0500 Subject: Re: [PATCH 4.10 000/167] 4.10.2-stable review To: Kevin Hilman , "kernelci.org bot" References: <20170310083956.767605269@linuxfoundation.org> <58c2b8ac.1f002e0a.ae306.aa13@mx.google.com> Cc: Greg Kroah-Hartman , lkml , Linus Torvalds , akpm@linux-foundation.org, Shuah Khan , patches@kernelci.org, Ben Hutchings , stable@vger.kernel.org, Andy Gross From: Guenter Roeck Message-ID: <1837c4b3-7f41-224a-bb04-e321ba407bd7@roeck-us.net> Date: Fri, 10 Mar 2017 17:04:27 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/10/2017 03:52 PM, Kevin Hilman wrote: > On Fri, Mar 10, 2017 at 3:24 PM, Kevin Hilman wrote: >> kernelci.org bot writes: >> >>> stable-rc boot: 541 boots: 6 failed, 500 passed with 34 offline, 1 conflict (v4.10.1-168-gcdc1f9d24aac) >>> >>> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.10.1-168-gcdc1f9d24aac/ >>> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.10.1-168-gcdc1f9d24aac/ >>> >>> Tree: stable-rc >>> Branch: local/linux-4.10.y >>> Git Describe: v4.10.1-168-gcdc1f9d24aac >>> Git Commit: cdc1f9d24aac385a7fe4611d7b42f51e20f49cdb >>> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >>> Tested: 101 unique boards, 25 SoC families, 30 builds out of 204 >>> >>> Boot Regressions Detected: >>> >>> arm: >>> >>> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: >>> am335x-pepper: >>> lab-baylibre-seattle: new failure (last pass: v4.10-21-gd23a9821d397) >> >> This one is a new regression, and a first attempt at bisect was >> inconclusive. > > Bisect fingered the commit below. I confirmed that reverting that > commit on top of stable-rc/linux-4.10.y gets this am335x-pepper > platform booting again. What's rather strange is that this boot test > is using a .cpio.gz initramfs, and not using any ext4 filesystem. > Does that even make sense ? Just wondering, after the problems we are currently experiencing with nios2. Those "bisected" as well to a commit associated with code which never executed. It turned out that the change in code size caused completely unrelated memory overwrites to be observed. Reverting the patch in question also seemed to "fix" the problem. Only, of course, that wasn't true. Maybe something similar is happening here ? Guenter > 04992982b8f8caf6c54531a23d3f9c2bc4d0a7d8 is the first bad commit > commit 04992982b8f8caf6c54531a23d3f9c2bc4d0a7d8 > Author: Theodore Ts'o > Date: Sat Feb 4 23:04:00 2017 -0500 > > ext4: fix inline data error paths > > commit eb5efbcb762aee4b454b04f7115f73ccbcf8f0ef upstream. > > The write_end() function must always unlock the page and drop its ref > count, even on an error. > > Signed-off-by: Theodore Ts'o > Signed-off-by: Greg Kroah-Hartman > > > Kevin >