[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2D6D38D9-FE06-4115-8FB2-48CB2FB19809@codeaurora.org>
Date: Tue, 24 May 2016 17:31:51 -0500
From: Matthew McClintock <mmcclint@...eaurora.org>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: Al Viro <viro@...IV.linux.org.uk>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c
> On May 24, 2016, at 2:36 PM, Larry Finger <Larry.Finger@...inger.net> wrote:
>
> On 05/24/2016 02:25 PM, Matthew McClintock wrote:
>> On May 24, 2016, at 2:16 PM, Larry Finger <Larry.Finger@...inger.net> wrote:
>>>
>>> On 05/24/2016 02:13 PM, Matthew McClintock wrote:
>>>> I’m seeing this too, same commit if you want another person to test/reproduce.
>>>
>>> If you do a pull today, does that fix your problem?
>>
>> Hmm, no. Which commit am I looking for? I’m on a56f489502e28caac56c8a0735549740f0ae0711
>
> Commit 84787c572d402644dca4874aba73324d9f8e3948 is working for me. I have a fixup in lib/iov_iter.c with a dump_stack() call if the fixup was needed. That dump is not triggered. I do not seem to have a56f489502e yet.
Still seeing the issue on top of tree and the above commit. Re-ran bisection just to be sure.
-M
Powered by blists - more mailing lists