linux-kernel - Re: [PATCH v3 1/5] gpio-langwell: initialize lock before usage

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 31 May 2013 14:01:18 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Grant Likely <grant.likely@...retlab.ca>
Cc:	David Cohen <david.a.cohen@...el.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/5] gpio-langwell: initialize lock before usage

On Wed, May 22, 2013 at 12:20 PM, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:

> Otherwise we will end up with traceback from LOCKDEP:

Andy do you consider this a regression that needs to go into fixes?

I.e. is this used in in-tree code and causing problems with v3.10...

I'm asking because it creates a mess as the rest of the series depend
on it.

It is currently applied for v3.11.

Yours,
Linus Walleij
--
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/