linux-kernel - Re: Regression in 3.0-git - bisected to commit dd4e5d3ac4a76b868daf30e35bd572def96c30ed

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] [day] [month] [year] [list]

Date:	Thu, 04 Aug 2011 11:00:53 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Regression in 3.0-git - bisected to commit dd4e5d3ac4a76b868daf30e35bd572def96c30ed

On 08/04/2011 10:19 AM, Peter Zijlstra wrote:
> On Thu, 2011-08-04 at 10:08 -0500, Larry Finger wrote:
>> The logs for a recent git pull from Linus's tree show the warning below. The
>> problem has been bisected to commit dd4e5d3ac4a7 with the commit message of
>>
>> ===============
>> lockdep: Fix trace_[soft,hard]irqs_[on,off]() recursion
>
> Thanks, but yes that's known, and a patch has been queued for merger
> that should solve this:
>
> https://lkml.org/lkml/2011/8/4/60

Sorry for the noise. I expected that this was a known problem and searched for 
it. I probably used the wrong number of digits in the hash.

Your patch does fix the issue for me.

Thanks,

Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/