linux-kernel - Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 May 2016 14:36:17 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Matthew McClintock <mmcclint@...eaurora.org>
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 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.

Larry