From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753625AbcEYBKl (ORCPT ); Tue, 24 May 2016 21:10:41 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:40526 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751515AbcEYBKk (ORCPT ); Tue, 24 May 2016 21:10:40 -0400 Date: Wed, 25 May 2016 02:10:36 +0100 From: Al Viro To: Matthew McClintock Cc: Larry Finger , LKML Subject: Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c Message-ID: <20160525011036.GB14480@ZenIV.linux.org.uk> References: <57437683.30008@lwfinger.net> <20160524001854.GW14480@ZenIV.linux.org.uk> <57447CE1.9020207@lwfinger.net> <6E57F7A4-59B0-46EA-9FFF-D0A4BA2D8E51@codeaurora.org> <5744A899.70503@lwfinger.net> <3988EB49-F17D-452B-A1AD-F202265B1BCA@codeaurora.org> <5744AD31.4090808@lwfinger.net> <2D6D38D9-FE06-4115-8FB2-48CB2FB19809@codeaurora.org> <20160524234133.GA14480@ZenIV.linux.org.uk> <1CDF0CFA-CCD2-440A-B956-2787BD8F2C4F@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1CDF0CFA-CCD2-440A-B956-2787BD8F2C4F@codeaurora.org> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 24, 2016 at 07:58:13PM -0500, Matthew McClintock wrote: > > > On May 24, 2016, at 6:41 PM, Al Viro wrote: > > > > Again, I understand what's going on kernel-side; the only tricky part is how > > to fix it without bringing the nasal daemons back. I think I have a solution > > and I'm going to post it tonight if it survives the local beating. In any > > case, the testcase above deserves being added to LTP - it's a real regression. > > I’m running a simple busybox rootfs with the following init script: > > https://gist.github.com/7b12fdb5d7def9a835291a79c060fa07 > > And inittab: > > https://gist.github.com/5a840b7eaa48f321836125f15147d0e9 > > Happy to turn on ftrace, dyndbg, and provide more logs. Slap the WARN_ON(!size); in the very beginning of iov_iter_advance(), see where it's triggered...