linux-kernel - Re: possible reason: unannotated irqs-off

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]

Message-ID: <560067EC.8060203@ti.com>
Date:	Mon, 21 Sep 2015 16:26:20 -0400
From:	Murali Karicheri <m-karicheri2@...com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: possible reason: unannotated irqs-off

On 09/21/2015 11:44 AM, Murali Karicheri wrote:
> Russell,
>
> On 09/18/2015 01:02 PM, Russell King - ARM Linux wrote:
>> On Fri, Sep 18, 2015 at 12:02:15PM -0400, Murali Karicheri wrote:
>>> While chasing a fix for a deadlock in netcp driver with debug options
>>> enabled, i bumped on another warning shown below.. Looks like I need to
>>> enable CONFIG_IRQSOFF_TRACER as well to get rid of this. Have anyone
>>> seen
>>> this? My google search showed me some connection with this option and I
>>> enabled it as well and I don't see the warning anymore. Any idea if
>>> this is
>>> a false alarm or a real bug? Looks like I need to enable
>>> CONFIG_IRQSOFF_TRACER as well. If so, I can send a patch. Either way
>>> let me
>>> know.
>>
>> Do you have this commit applied?
>
> No. We are using v4.1.x.
>
>>
>> commit 3302caddf10ad50710dbb7a94ccbdb3ad5bf1412
>> Author: Russell King <rmk+kernel@....linux.org.uk>
>> Date:   Thu Aug 20 16:13:37 2015 +0100
>>
>>      ARM: entry: efficiency cleanups
>>
>
> I have cherry-picked this one, but ran into some conflicts which I have
> fixed. Will try and let you know.
>
Yes. This fixes the issue. I will request Greg.H to apply this to 4.1.y 
stable.

Murali

> Thanks


-- 
Murali Karicheri
Linux Kernel, Keystone
--
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/